The basics of the article sum up the efforts that as a programmer I am constantly making. To sum it up a programmer must be lazy – to prevent being repetitive in his work, repeating oneself over and over means that you have to maintain the work everywhere, doing it once and re-using it the lazy way ensures that it is inevitably clean and tidy code, leading to a better application that is easier to debug.  A programmer must be dumb so as not to become too "smart" to learn the latest techniques and technologies.  He must dumb down, when asked to solve a problem, asking the simple questions to ensure that the parameters of the problem are set out in full and not someones impression of the parameters of the problem.

It is funny how on reading this, I understood exactly what the guy is saying.  I am constantly fighting to stop myself repeating code because it is easier to write if I just copy it.  I would also say 90% of my support queries can be answered using the simple question method – I even had one where they phoned up and said they can't access the software or any other web page – he had forgotten to plug in his network cable.  Ok, so that is a little exaggeration on my part, but it is so easily done, and the simple answer is usually the right one.  I recommend the article if you have time for a quick read, I will be one happy programmer the next someone calls me either lazy or dumb!!