Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Do Coding Standards Make a Difference?

Posted by Soulskill on from the everybody-do-it-wrong-the-right-way dept.

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

2 of 430 comments (clear)

  1. Re:After 42 yrs programming I say... by man_of_mr_e · · Score: 5, Interesting

    Coding standards were largely developed to prevent developers from reformatting each others code in a format war.

    Joe works on code, checks it in. Bill gets a task to work on that code, doesn't like Joe's formatting, so he reformats, checks that in.. Joe works on the code again, finds it's been reformatted, then he reformats it again.

    This is hell when doing diff's and figuring out what changes from version to version. Coding standards help to prevent that.

    Another reason for coding standards is to set a level playing field for everyone.

    --
    If you need web hosting, you could do worse than here
  2. Re:After 42 yrs programming I say... by Decameron81 · · Score: 5, Interesting

    THE reaSON WHy coDiNg standards_exist is thatTheyIncrease THE_REaDABILITY oF YOur cODe.

    --
    diegoT