I get bombarded with questions like these all the time from my fellow developers: * "Which is faster, .Count() or .Any()?" * "Should I use a Redis database for my reads rather then SQL Server? I heard Redis is amazingly fast." * "Won't [Snippet X] be faster than [Snippet Y] because it's more
It is the elephant in the room, the monster in the corner, the darkness waiting to claim your job. It sneaks up on you quietly, stealthily, like a lion waiting to pounce. It is endless, varied, impossible to predict and harder to defend against. Everyone has encountered it, battled it,
I stumbled across an interesting StackOverflow thread [http://stackoverflow.com/q/24018008/106356] earlier this week. I had to read it a few times to notice what bothered me: it turns out that there is a status code for HTTP 418 "I'm a teapot". Why in the world would HTTP
I'm mostly a server-side developer, but occasionally I delve into the wild world of client-side programming. Each time I do, I get bombarded with blog posts and tweets and advocates [http://www.exceptionnotfound.net/zealotry-has-no-place-in-software-development/] , each hyping their own preferred JavaScript framework. Use Angular [https://angularjs.org/], they said. No,
Have you ever been hunting a bug and been absolutely sure that it was in someone else's code, only to find out that, nope, it was in yours all along? I sure did. Come along with me as we explore my latest minor failure and remind ourselves that, most of