Guides

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

• Best Practices
• Code Review
• Protocol
  • Communication
  • Git
  • iOS
  • Open Source
  • Product Review
  • Rails
• Security
• 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.

Contributing

Please read the contribution guidelines before submitting a pull request.

Credits

Thank you, contributors!

License

These guides are based on thoughtbot's guide docs.

Changed mades on these docs are © 2014-106 Yellowen. It is distributed under the Creative Commons Attribution License.

The names and logos for Yellowen are trademarks of Yellowen.