Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Ask Slashdot: Do coding standards make a difference?

Anonymous Coward writes | about 2 years ago


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?"

Sorry! There are no comments related to the filter you selected.

Not sure if troll but... (0)

Anonymous Coward | about 2 years ago | (#42353623)

It's a lot easier to work with code written by a large development team if you don't have to remember which modules use what name standards, and many people find code with varying formatting rules more difficult to read than its consistently formatted counterpart. Although what standard the group follows is arbitrary, consistency is useful. I see no fault with your coworker reviewing to the code standard before reviewing the algorithm itself.

go (1)

tracius01 (2541214) | about 2 years ago | (#42357145)

go lang has such a tool "gofmt" and here the war is over. one style to rule them all!
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?