Tripped across this on WardsWiki just now. #5 is my favorite as its often forgotten in the noise.
http://www.c2.com/cgi/wiki?UncleBobOnCodingStandards On coding standards: 1. Let them evolve during the first few iterations. 2. Let them be team specific instead of company specific. 3. Don't write them down if you can avoid it. Rather, let the code be the way the standards are captured. 4. Don't legislate good design. (e.g. don't tell people not to use goto) 5. Make sure everyone knows that the standard is about communication, and nothing else. 6. After the first few iterations, get the team together to decide. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ Abandon failing tactics.
