The Agile Way

The Agile Way

Share this post

The Agile Way
The Agile Way
Human Considerations in Mandatory Formal Code Reviews - Part 2 *

Human Considerations in Mandatory Formal Code Reviews - Part 2 *

Most mandatory formal code reviews are ineffective, costly, and often create disharmony within the team.

Zhimin Zhan's avatar
Zhimin Zhan
Aug 18, 2025
∙ Paid

Share this post

The Agile Way
The Agile Way
Human Considerations in Mandatory Formal Code Reviews - Part 2 *
1
Share

Continue from Part 1, the human factors to consider for the mandatory formal code review process:

  • 4. Software Engineers: Would you like to pause your current work to review a colleague’s PR?

  • 5. Do you really think software developers can effectively spot the majority of real issues just by eyeballing the code changes in a PR?

  • 6. Do software developers want to carry the extra responsibility for someone’s code?

  • 7. Software engineers are evaluated based on the quality and functionality of their code, not the number of PRs they review.


4. “Software Engineers: Would you like to pause your current work to review a colleague’s PR?”

For most software engineers, the answer to the question above—regardless of whether others think they should or shouldn’t—is ‘NO.’

Keep reading with a 7-day free trial

Subscribe to The Agile Way to keep reading this post and get 7 days of free access to the full post archives.

Already a paid subscriber? Sign in
© 2025 Zhimin Zhan
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share