Google engineering practices are now open source. The pages in this section contain recommendations on the best way to do code reviews, based on long experience.
The primary purpose of code review is to make sure that the overall code health of code base is improving over time. First, developers must be able to make progress on their tasks. If you never submit an improvement to the codebase, then the codebase never improves. Also, if a reviewer makes it very difficult for any change to go in, then developers are disincentivized to make improvements in the future.
The guide has these sections:
- The standard of code review
- What to Look For In a Code Review
- Navigating a CL in review
- Speed of code reviews
- How to write code review comments
- Handling pushback in code reviews
Excellent guide!
[Read More]