Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - Ask Slashdot: Do coding standards make a difference? 2

Submitted by Anonymous Coward
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.

Ask Slashdot: Do coding standards make a difference?

Comments Filter:

"Kill the Wabbit, Kill the Wabbit, Kill the Wabbit!" -- Looney Tunes, "What's Opera Doc?" (1957, Chuck Jones)

Working...