Unity3D is a powerful suite of tools (Project IDE, Code IDE, and run-time) for game development. Unity supports several languages, but the community consensus is to use only C#. Having good coding standards and an established project structure is beneficial to your project and your team.
Regardless of which convention you choose to use for Unity or other platforms, having some sort of convention is considered a good idea by the majority of the development community.
- Consistency – The code base as consistency in presentation regardless of team location, spoken language, or individual programmers .
- Integration – The code, the review of the code, and your team are more tightly integrated. Theoretically, the code is more interoperable (copy/paste) and mutually intelligible.
- Communication – Developers more implicitly understand each other in written and verbal communication.
Few developers argue the benefits of coding conventions, yet many argue if the time and discipline required is worth it. More contentious yet — what are the criteria of a good standard? A few criteria most people can agree on are here.
- Consistency – Whatever rules there are should be applied evenly and applied everywhere.
- Pragmatism – The convention should be concerned with ‘important’ things and nothing else.
Read my complete article on coding standards…