Skip to content
J·BJon BishopIndependent growth marketer

Developer experience · Exploratory mixed-method industry case study combining 12 interviews, a survey, and analysis of review logs.

Modern Code Review: A Case Study at Google

Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice (ICSE-SEIP '18) · 2018

Caitlin Sadowski, Emma Söderberg, Luke Church, Michal Sipko, Alberto Bacchelli

Summary

Code review at Google serves more than bug finding: the study examines motivations, practices, developer satisfaction, and challenges in a mature, lightweight, tool-based process. The evidence highlights code review's normative, educational, testing, accident-prevention, and gatekeeping functions, alongside recurring challenges.

For your marketing

Possible founder application

Use the findings to design review workflows and tooling around reviewability, education, shared code ownership, norms, and reviewer experience—not only defect detection—and to instrument satisfaction and friction at scale.

Reported result

What the study found

Code review at Google serves more than bug finding: the study examines motivations, practices, developer satisfaction, and challenges in a mature, lightweight, tool-based process. The evidence highlights code review's normative, educational, testing, accident-prevention, and gatekeeping functions, alongside recurring challenges.

Research question

What the authors investigated

Why did Google introduce modern code review, what are its current practices, and what satisfaction and challenges do developers report after the process matured?

Design

Exploratory mixed-method industry case study combining 12 interviews, a survey, and analysis of review logs.

Sample and setting

Google software development; 12 interviewees, 44 survey respondents, and review logs covering 9 million reviewed changes.

Scope and transfer

Limitations to keep in view

Single-company case study; interviews and survey are relatively small and potentially subject to selection or self-report bias; log analysis shows review activity but cannot by itself establish causal effects on productivity or quality.

Research sources

Title, author list, venue, year, DOI and pages: https://doi.org/10.1145/3183519.3183525; accessible abstract, methods and sample: https://research.google/pubs/modern-code-review-a-case-study-at-google/ Firecrawl research job 01a14371-854f-71aa-ba3d-455ec397717d returned this citation and metadata.

Additional research source ↗

Prefer to write? Send Jon a message.