- "Ensure that reviews are two-way. Never have people who only review and people who only get reviewed."
- "Always focus on the code and not the person who wrote the code."
- "Make the reviews small, frequent, and informal. Marathon group sessions in rooms make people defensive."
- "Frame things as questions and suggestions rather than orders and accusations. Ask that others do the same."
- "Automate as many checks as possible so that reviews don't focus on simple details."
- You can frame the review as optional "asking for advice" instead of a gatekeeper approach of "getting the code approved"
- Says that the potential harm of the bad approach is worse than taking up the risks, that is taking the risks that come with the policy of not requiring a code review for each and every commit.
He has the following suggestions: