This article is wrong. It assumes that priorities are the same for all programming. When programming you should be programming to a set of priorities i.e.: s

This article is wrong. It assumes that priorities are the same for all programming. When programming you should be programming to a set of priorities i.e.: software performance/speed maintainability security reliability conformance to organisational statndards conformance to testing requirements time to market compatibility research/problem solving prototyping probably more... The priorities of your project dictate your approach. This guy says one size fits all.