The Minds Behind Code Review – 7 People Redefining Software
Seven researchers and practitioners helped evolve code review from formal inspections into lightweight, tool-based collaboration around nearly every software change.
TL;DR
Seven researchers and practitioners helped evolve code review from formal inspections into lightweight, tool-based collaboration around nearly every software change. [1][2]
Why you should read it anyway
Code review creates a second line of reasoning before software reaches users. It catches defects, spreads knowledge, enforces local conventions, and makes design decisions visible to more than one person.
Imagine where Code Review would be without them
Without this lineage, teams would still read each other’s code, but formal inspections, lightweight review workflows, empirical review research, and organization-wide review norms would have matured much more slowly.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 5–9 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, systems, research, and practices.
The 7 people behind Code Review
1. Michael Fagan
Why they matter: created the formal software inspection process at IBM, establishing a disciplined peer-review method for finding defects before testing.[1]
2. Tom Gilb
Why they matter: advanced software inspection practice through methods, measurement, and quality-focused engineering guidance.[2]
3. Dorothy Graham
Why they matter: helped spread structured inspection and peer-review practices through software quality training and writing.[3]
4. Caitlin Sadowski
Why they matter: led influential empirical work on modern code review at Google, documenting why lightweight review became a default engineering practice at massive scale.[4]
5. Alberto Bacchelli
Why they matter: co-authored major studies of modern code review and helped establish an empirical research base around its benefits and challenges.[5]
6. Peter Rigby
Why they matter: conducted influential research on peer review in open source and industrial projects, helping compare lightweight review with formal inspection traditions.[1]
7. Christian Bird
Why they matter: contributed broadly to empirical software engineering and collaborative development research, including the social and organizational dynamics surrounding code changes and review.[2]
How they each differ from one another
Fagan established formal inspection; Gilb and Graham broadened disciplined review practice; Sadowski and Bacchelli studied modern tool-based review; Rigby connected open-source peer review with industrial methods; Bird examined collaborative engineering at scale.
Final Take
Modern code review works because it converted peer scrutiny from an occasional quality ceremony into a routine part of changing shared software.
Works Cited
- 01
- 02Google Research — Modern Code Review: A Case Study at Google research.google
- 03Microsoft Research — Code Review studies microsoft.com
- 04
- 05IEEE Software — Peer review and inspection research computer.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead