The trouble with this article is that it appears to have been written by a poor programmer - where is the requirements analysis etc?

Where are the definitions? I mean, which definition of 'Good Programmer' are we discussing? The kind that spend all of their time writing books, giving lectures, and producing nothing? The kind that never make a mistake, and produce 'beautiful' programs? Or the kind that get stuff out on time, are continuously learning, and getting pay increases every year?

For me 'continuous improvement' is probably the most important phrase in any business.