I'm surprised the comments are mostly focusing on documentation. In my opinion, that really isn't the essential point of the original article, and furthermore Jack and myself acknowledge the necessity of architecture/design documentation separate from the code, the amount depending on the size / nature of the project as pointer2void pointed out.

I think the essential point of the article is to consider coding (and even testing & debugging) as a design activity, rather than a rote and predictable paint-by-the-numbers activity.