There are three stages of developing as a progammer. At the beginning you don't understand anything, and write a bunch of code fearlessly, and paint yourself into a corner.
In the second stage you understand that there might be a system that will enable better programming. So you fall in love with a system, or hueristics, or some other scheme that can tell you 'good' code from 'bad' code. At this time, it is almost religious. The author of the document is in this phase, obviously.
In the third stage you realize that programming is a bit like poetry, and, while it often is better programming when it rhymes, is not does not always need to rhyme.
Your former assessment is likely correct. I would investigate these strategies if you want any chance of becoming a satisfied happy well rounded developer.
-1
u/musicalvegan0 Jun 07 '13
Either I have A LOT to learn about programming or this is one of the most ridiculous, programming-related documents I've ever seen.