At Rocket we have established coding style guides for all of the languages we work with. We wanted to share some of these guides and our rationale for having them.
A good guide will make your code more readable and code reviews more pleasant. It will also promote good coding practices to everyone you work with, including new members of your team.
Here is our Swift style guide. We'd love your feedback -- feel free to fork/modify etc.
Swift Style Guide (Github)
But, a style guide is not a panacea. It won't necessarily make your code more bulletproof, faster or better. In fact, as a wise man (Ralph Waldo Emerson) once said....
A foolish consistency is the hobgoblin of little minds
However, we believe having a guide demonstrates a level of care and passion for how you and your team craft code. We want to make sure that our software is beautiful inside and out. For, another wise man (Steve Jobs) said...
For you to sleep well at night, the aesthetic, the quality, has to be carried all the way through.
In the future we will discuss other types of guides that we use that have a significant impact on the quality of a project.