For all projects we adhere to a strict naming convention and methodology for coding.
Our coding-rules have been developed over many years and have proved their worth time and time again.
This rigorous approach results in robust solutions with lower maintenance and easier expansion.
It might seem unnecessarily laborious but, given the experiences we have had when developing with less rigorous developers, we know the value of sound methodologies.
There are some basic rules which even some of the apparently highly qualified practitioners fail to understand. We have even named them!
In any choice of validation routine (such as checking the validity of a Credit Card), at the point when all the checks have been made and failed the default action should also be a failure. To do otherwise is known as a "Chadism".
Naming of objects (database tables, variables etc...) is very important for code legibility, ease of maintenance and error minimization. We had an experience where a programmer was told to make sure he spell-checked all names he used. Sadly his grasp of the English language was not high and as a result instead of "CompaniesInQueue" he wrote "CompaniesInQueer". This is known as a Vadism.