Hey There! A common, tedious, horrible task when developing code in a team is being able to understand others. Why? Well, everybody think different. Your team thinks different. You think different. That's why it's really necessary to stablish a set guidelines and standards - A Coding Convention - that can be used by anybody, and we can make all those not understandable code something nice and usable. Let's start with a really simple definition of what a coding standard is:

Coding conventions are a set of guidelines for a specific programming language that recommend programming style, practices, and methods for each aspect of a program written in that language. These conventions usually cover file organization, indentation, comments, declarations, statements, white space, naming conventions, programming practices, programming principles, programming rules of thumb, architectural best practices, etc. These are guidelines for software structural quality. Software programmers are highly recommended to follow these guidelines to help improve the readability of their source code and make software maintenance easier. Coding conventions are only applicable to the human maintainers and peer reviewers of a software project. Conventions may be formalized in a documented set of rules that an entire team or company follows, or may be as informal as the habitual coding practices of an individual. Coding conventions are not enforced by compilers.

What's all of that fancy language?

Well, let's take it simple. Think of the conventions as a set of rules that you should follow when programming. It covers spacing, indentation, styles, practices and much more for each specific language. This will always allow us to ensure to always get the most quality/time relation possible, while not leaving behind costs or portability. And let's take a quick view at the last sentece of our fancy phrase: Coding conventions are not enforced by compilers. This means that this is usable for Other humans to understand it, but once everything is passed to the compiler, it will be no more.