An anonymous reader writes "If you've been hired by a serious software development house chances are one of your early familiarization tasks was to read company guidelines on coding standards and practices. Some basic guidelines such as gotos being off limits except in specific circumstances or that code should be indented with tabs rather than spaces or vice versa were laid out, and perhaps some more exotic or less intuitive practices as well. Maybe continue or multiple return statements are off limits. What standards have you found worked well practice, increasing code readability and maintainability, and which only looked good on the proverbial paper?"
This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.
... if you use source control, and insert your own personal 'layout standard' as a process that sits inbetween the respository and the programmer.
For example, we used to use any layout style we liked, but when someone else checked-out our code it would go through a version on indent http://www.gnu.org/software/indent/ [gnu.org] which the individual programmer had 'tweaked' with their own preferences.
Result: layout-religion went away, and we were all more productive.
Layout doesn't matter ... (Score:1)
For example, we used to use any layout style we liked, but when someone else checked-out our code it would go through a version on indent http://www.gnu.org/software/indent/ [gnu.org] which the individual programmer had 'tweaked' with their own preferences.
Result: layout-religion went away, and we were all more productive.