September 20, 2006
Coding Conventions: Make Them Agile
The End of "Thou Shalt Not..."
You'll notice that these 10 items have nothing to do with bracketing styles, nor is there a single mention of goto in this entire document. This is because you have to trust your team's ability to make sound decisions, and for the coding conventions to apply a light touch. You can't sweat the small stuff, like having/not having a space between an if and its corresponding parenthesis. After all, the developers all have their own particular coding preferences and you'll needlessly spend an enormous amount of effort trying to change them.
Instead, concentrate on creating an agile coding convention that meets the needs of your agile organization.
Previous Page |
1 Introduction
|
2 Rules 1-3
|
3 Rules 4-6
|
4 Rules 7-10
|
5 Conclusion
