Code Reviews by Phase and Expectations

Code reviews are amazing for many reasons. And everyone on the team should contribute. Interestingly, the behavior of an engineer with respect to code reviews changes based on seniority or tenure within a team or code repository. I like to refer these changes as “phases”.

This document attempts to describe the expectations of each phase and help provide guidance on maximizing code reviews on your team.


Learning Phase

Enforcement Phase

Leadership Phase

Thought Leadership Phase

Code reviews are great and can be the single biggest thing you can do to improve your code.

The Wisdom of David Henke
Don't Ask for Feedback, Ask for Advice