|Perl Monk, Perl Meditation|
Re: Why Create Coding Standards and Perform Code Reviews?by BrowserUk (Pope)
|on Jul 03, 2009 at 15:15 UTC||Need Help??|
I don't suppose you'd feel like posting your coding standard here? I'd love to pick it over :)
The trouble with coding standards is that they all too often become sticks for keeping the serfs in line in surrogate fiefdoms. One man decides that his style is the standard and everyone else must adopt it. The assumption being that cos he's the boss, he knows best.
Somethings code standards can mandate are Good Things:
Conversely, I've been subjected to some horrible "standards": 2-char indentation; Hungarian notation; Camel_Case_Plus_Underscores; mandatory 24 line block comments for every function or method; and many more.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.