Guides

Guides for getting things done, programming well, and programming in style.

• Protocol
• Code Review
• Best Practices
• Style

High level guidelines:

• Be consistent.
• Don't rewrite existing code to follow this guide.
• Don't violate a guideline without a good reason.
• A reason is good when you can convince a teammate.

A note on the language:

• "Avoid" means don't do it unless you have good reason.
• "Don't" means there's never a good reason.
• "Prefer" indicates a better option and its alternative to watch out for.
• "Use" is a positive instruction.

Credits

Thank you, contributors!

This version of Guides is maintained by TGFI, inc.

License

This is a fork of the Thoughtbot Guides repository. It is distributed under the Creative Commons Attribution License.