I recently participated in my company’s 24 hour hackathon. I pulled together my tweets on Storify here: https://storify.com/g33klady/jurassic-hack-ql-technology-24-hour-hackathon-of-2 It was a super cool experience, and I’m looking forward to learning more 😀
2017 was eventful, to say the least. I submitted 8 talks to 6 conferences. I was accepted to 5 of those conferences, gave an extra talk at one of them I wasn’t planning on, and was invited to speak at another with a brand new talk. I spoke on life lessons at KalamazooX, making your …
I signed up for the C# Advent Calendar with this post – be sure to check out the rest of the blog posts in the calendar! This post assumes you’ve got some experience with C# and Visual Studio, so I won’t be over-explaining some things. Comment if you get stuck or have questions! If you’re …
In my Testing RESTful Web Services talk, I touch on service virtualization briefly, and I include a short demo of using Fiddler‘s AutoResponder. I’ve been meaning to look into other (free) tools but haven’t had the chance.
After a question on the Testers Slack, I realized I could do a short blog post on how I demo’d AutoResponder in my talk. It gives a quick idea of the tool and one way you could use it. I love Fiddler*, and there’s so much more you can do than what I’ve been able to use. Please don’t take this post as a “this is the only way you can do things” – I’ll be the first to admit that even though I’ve used Fiddler for years, I feel like there’s so much more to know about it!
*Note: I am not paid by Telerik/Progress for my endorsement; I just love the tool 😀
Fourteenth in the HTTP Status Coop series is 503 Service Unavailable! The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. via Wikipedia Cooper says “no way!” 😀 For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on …
Lucky Thirteen, on a Monday the 13th, of the HTTP Status Coop series is 500 Internal Server Error! And no, I didn’t plan it that way! A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. via Wikipedia For the entire HTTP Status Coop series that’s been released …
Twelfth in the HTTP Status Coop series is 413 Request Entity Too Large (or Payload Too Large)! The request is larger than the server is willing or able to process. Previously called “Request Entity Too Large”. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop …
Eleventh in the HTTP Status Coop series is 408 Request Timed Out! The server timed out waiting for the request. According to HTTP specifications: “The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.” via Wikipedia For …
Tenth in the HTTP Status Coop series is 406 Not Acceptable! The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. via Wikipedia Clearly the request was *not* acceptable for Cooper… For the entire HTTP Status Coop series that’s been released so far, head over to …
Ninth in the HTTP Status Coop series is 404 Not Found! The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my …