This document is a rewritten and very much expanded version of a coding standard I co-authored with Roneel Achal in 1999. Since that time, my knowledge and level of experience have increased; thusly I was able to include significantly more material in this new version. This document has increased in length by a factor of 6 over the original version that Roneel and I composed long ago.
It should also be noted that Darren Holloway directly contributed some excellent material to this coding standard. Mr. Holloway's contributions would include the sections [in the Java standard] entitled always comment bug fixes and place variables on the right side of relational operators.
A friend once remarked that only rich people can afford poor programmers. This comment indicates the long known truth that poor initial coding and/or design ensures that a piece of software will be expensive and built to stay that way! Software historically incurs much of its cost in the maintenance phase of its life - the part that happens after the system has been created and deployed. Hence if one endeavours to build systems with a low overall lifetime cost one must strive to get it right the first time. One way to achieve this lofty goal is to have a simple set of standards that developers must adhere to; the standards must be simple or they won't be used.
These coding standards are intended to establish a set of guidelines one should follow when coding anything webbish. The content of these coding standards outlines a set of best practices. It has been demonstrated that the use of these guidelines and best practices provide more robust code that has a lower lifetime cost.
In instances where the coding standard is unclear, one should consult a senior developer (if possible). One should then inform the author of the lack of clarity in the standards so that they may be improved.