A collection of rules for various languages that are designed to help spot problems, untangle code and provide consistency.
In order to maintain a high level of quality, the Tests-Always-Included team adheres to this style guide. It helps keep our code consistent and has been designed to train your eyes to automatically spot problems. Like all style guides, it is heavily biased, but the rules have been growing slowly and deliberately in the hopes that we will raise the bar and produce better results.
To get started, you should first get familiar with the style guide’s goals. After that, most of the rules are embodied within the general rules.
When you get to specific languages and techniques, we have individual guides.