One of my ex-coworkers emailed me this photo. The subject of the email was: Winner of “not my job” award.
When I looked at this photo, the word “laziness” started flashing in my mind. My thoughts then wandered to laziness as it related to programming. I then asked myself: what is laziness in programming? Here are a few thoughts:
Throughout my career I was guilty of being lazy. But some may argue that good programmers are not only lazy, but also dumb:
…for a lazy programmer to be a good programmer, he (or she) also must be incredibly unlazy when it comes to learning how to stay lazy â€“ that is, which software tools make his work easier, which approaches avoid redundancy, and how he can make his work be maintained and refactored easily.
…a good programmer must be dumb. Why? Because if heâ€™s smart, and he knows he is smart, he will: a) stop learning b) stop being critical towards his own work… a good programmer, when confronted with a problem from management, will adopt this mindset of being dumb; he will start asking the most simple, child-like questions. Because he doesnâ€™t accept the parameters suggested to him that someone thinks make up the problem.
So, you should always try to be lazy in an “unlazy” way, and dumb in a smart way.