There can be a tendency to over-engineer coding standards to the point where they get in the way of writing code.
I agree with Jozz’s comment. You can look at all the recommended standards, pick one and force it upon your coders or you can get your team involved in the process.
In my experience, the best way to get a team engaged is to have the team come up with the idea and the benefits of adoption. Your existing talent is your best resource. Likewise, they can be your ultimate enemy if you force them down a path they don’t buy into.
So, take a look at your existing coding variants and get the team together for some vibrant discussions on:
- The reasons for adopting a coding standard.
- Essential considerations in standardization.
- Surfacing any insecurities in the team surrounding this issue.
- Finding a point of agreement. What's important and what's not.
- Establishing some corporate objectives so everyone feels like they are working towards a common goal.
- Get the team to sell the benefits of standardization to themselves.
The most important objective must be to establish a ‘standard’ that best serves your team and your company.
