Most of the times when I code, I actually think that it is good that the language is structured the way it is, because the purpose of the code is so obvious, so I don’t have to worry about the person who will maintain it. I don’t know about you, but sometimes I really get struck by the feeling that some particular piece of code, will be a problem for the one that is going to understand what is going on, to be able to maintain. Maybe the code is segmented in the wrong way or for the wrong reason, or maybe the code is an invention that might as well be credited to Dr. Horrible. I stumbled upon this tip-of-the-day, and realized that I’m not alone:

Always code as the if the person who will maintain your code is a maniac serial killer that knows where you live.

One thought on “The maintainer might be a maniac serial killer

  1. Anna Forss says:

    As a tester, one of my biggest problems is when I try to catch multiple bugs at the same time, two bugs working “together” is just a perfect horror story which keeps you from seeing the pattern to corner a bug.

    My favorite in this context was when the developers also had a check in policy that comments were mandatory. The comment for the entangled code was
    “[Object ID] is calculated using some kind of logic.”

    Well, one can only hope so

Leave a Reply

Your email address will not be published. Required fields are marked *