Dogmatic principles and software development

Graham Lee:

You can find plenty of dogmatic positions in software development, in blogs, in podcasts, in books, and even in academic articles. “You should (always/never) write tests before writing code.” “Pair programming is a (good/bad) use of time.” “(X/not X) considered harmful.” “The opening brace should go on the (same/next) line.”

Grahams’s post is short and worthwhile read.

Here’s the point in a nutshell:

Pronouncements like coding standards and methodological commandments can be useful, but not on their own…They can be presented as a small part of a bigger picture, to help competents progress to proficiency. As isolated documents they are significantly less valuable.