An anonymous reader writes: Every shop I've ever worked in has had a "Coding Style" document that dictates things like camelCase vs underscored_names, placement of curly braces, tabs vs spaces, etc... As a result, I've lost hundreds of hours in code reviews because some pedant was more interested in picking nits over whitespace than actually reviewing my algorithms. Are there any documents or studies that show a net productivity gain for having these sorts of standards? If not, why do we have them? We live in the future, why don't our tools enforce these standards automagically?

This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.