12 principles that guide programming at Google

1–2 minutes

·

·

1. All developers work out of a ~single source depot; shared infrastructure!

2. A developer can fix bugs anywhere in the source tree.

3. Building a product takes 3 commands (“get, config, make”)

4. Uniform coding style guidelines across company

5. Code reviews mandatory for all checkins

6. Pervasive unit testing, written by developers

7. Unit tests run continuously, email sent on failure

8. Powerful tools, shared company-wide

9. Rapid project cycles; developers change projects often; 20% time

10. Peer-driven review process; flat management structure

11. Transparency into projects, code, process, ideas, etc.

12. Dozens of offices around world => hire best people regardless of location

(via Google Operating System

Leave a comment

Feature is an online magazine made by culture lovers. We offer weekly reflections, reviews, and news on art, literature, and music.

Please subscribe to our newsletter to let us know whenever we publish new content. We send no spam, and you can unsubscribe at any time.

← Back

Thank you for your response. ✨

Designed with WordPress.