http://www.perlmonks.org?node_id=777381


in reply to Best practices, revisited

No battle plan survives contact with the enemy.(Helmuth Karl Bernhard Graf von Moltke)
Why would it be different with "Best Practices"? The value of Damian's book lies in the fact that he explains why he considers some practices "best". You may agree or not agree, but it is not presented as a fixed list never to be changed nor to be doubted.

If you find that a rule or a practice doesn't fit your style, why shouldn't you change it? But your argument to change it should be at least as good as the argument that imposes it.

For instance I'm a terrible typist (as all who read my CB-postings will readily agree), so I wouldn't think of writing even small scripts without "use strict;. On the other hand I rarely if ever "use warnings;"

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James