What you should do and not do when implementing Conventions in programming:
- Do value your programming conventions
- Don't forget: naming conventions, quality assurance rules and development guidelines should be well thought through at the beginning of a project. They should be communicated to all involved clearly.
- Do make sure that changes to conventions are done seldomly and never unannounced. It's a good thing to review conventions once on the way - it's a bad thing to "liquify" your conventions
- Don't apply your conventions after finishing the developments - naming conventions are a starting point issue. It is to be regarded as an ongoing theme, implemented from the beginning, not applied at the end. Known pitfall: apply naming conventions after testing the product.
- Do keep it sweet and simple - clarity above all.