I was re-reading the fantastic piece by Peter Welch called Programming Sucks [http://www.stilldrinking.org/programming-sucks], which is a classic despite it being only two years old. In the piece, Mr. Welch repeatedly demonstrates why programming (and the atmosphere surrounding it), well, sucks, which results in simultaneously hilarious and
I am a perfectionist. I know this, I accept it, and it still bites me in the ass. I want my code to be The Perfect Code, unbreakable, like a flawless diamond in a sea of cubic zirconium. I spend entirely too much time trying to cut that diamond from
A most interesting blog post was written a couple of days ago, and while I understand the author's frustration, I do not agree with his conclusion. The developer in question is Rob Ashton, who wrote a post [http://codeofrob.com/entries/why-you-cant-be-a-good-.net-developer.html] attempting to figure out why people
I went through a phase earlier in my career [http://www.exceptionnotfound.net/be-like-us-or-else-desperation-failure-and-new-job-regret/] where I thought design patterns were the be-all, end-all of software design. Any system which I needed to design started with the applicable patterns: Factories, Repositories, Singletons, you name it. Invariably, though, these systems were difficult
Use these handy memes to explain to your friends and coworkers just what it is you do all day. Here's the text-only version of this post [http://www.exceptionnotfound.net/useful-software-development-analogies]. Writing Code Image is modified from KUKA Industrial Robots IR.jpg [https://commons.wikimedia.org/wiki/File:KUKA_Industrial_