It can be really tedious to define coding standards to the finest detail. The following rule covers about 80% of what you really need to know:
Do unto your code as you would have others do
This rephrasing of the Golden Rule gets to the heart of what standards are all about. Whatever code you write, realize it is something that you are inflicting on other developers further down the line. Think of it as your legacy, because legacy code is what it is. Imagine yourself having to maintain the code (and you may, in fact, have to), and ask yourself if that’s code you can work with.
Also keep in mind that to some degree, you are setting the standards for all work that follows, especially considering the corollary part of this rule:
Do unto the code as others have already done
If code already exists in the project, chances are there a slew of already-established coding conventions. Before writing a single line of code in a new project, take a look around at what’s already there. Ask yourself some questions, like:
- How is everyone formatting their code?
- Which libraries are they already using?
- Are there already examples of how to do what I have to do?
- What are the overall design patterns, application layers, and so on that are already in force?
- Will I have to come up with some new conventions or solutions that others will have to follow?
By looking around, you can save yourself a LOT of time in terms of decision-making for insignificant issues (8-ball decisions), and may come up with examples that solve the majority of your work right off the bat. If you find that you need to create some new conventions, try to follow the “feel” of the code that has already been established. Otherwise, you’re good to go – just remember the Golden Rule!