Guides

Guides for programming like a boss, to the highest standard.

• 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 a 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.

Contributing

Please read the contributing guidelines before submitting a pull request.

Credits

Thank you, contributors!

In particular: if you have commit access, please don't merge changes without waiting a week for everybody to leave feedback.