Code review — how we do it and why it's essential

Since moving to Git we have made pull requests a mandatory part of our workflow. No code gets into develop without a review. After six months we’re sharing our experience.

Process¶

Feature branch, code, push, pull request. At least one reviewer approval required. Comments, fixes, approval, merge.

Checklist¶

Does it fulfill the user story? Unit tests? No code duplication? Clear naming? Security issues? Error handling? Readability?

Culture¶

Review is not a critique of the author, it’s an improvement of the code. Constructive tone. Not “this is wrong” but “have you considered this approach?”

Results¶

Average of 2.3 bugs per PR found before merge. Knowledge sharing. Consistent codebase. Average review time: 30 minutes.

Rules¶

1. Review within 24 hours. 2. Small PRs (under 200 lines). 3. Descriptive PR description. 4. Constructive tone.