Style guides are integral to creating high quality, consistent software across the board.
When it comes to multiple developers working on the same project, everyone has their own ways of styling and writing their code that is different from everyone else. This causes issues when you have multiple styles of code in one project, making it messy and hard to understand.
Having a style guide that we all follow means that all the project’s source code is consistent across the board and means that a developer joining the project will not have to battle through multiple different styles of writing, only to add their own style and complicate the project further, all of this leading to eventual software rot.
The following style guides are currently outlined: