Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 280

The DOI matches its Crossref record; 47 of the 47 references it cites were found in a registry or an index.

Modern code review: a case study at google

Open access
Sadowski, Caitlin, Söderberg, Emma, Church, Luke, Sipko, Michal, Bacchelli, Alberto·2018·Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice

Abstract

Employing lightweight, tool-based code review of code changes (aka modern code review) has become the norm for a wide variety of open-source and industrial systems. In this paper, we make an exploratory investigation of modern code review at Google. Google introduced code review early on and evolved it over the years; our study sheds light on why Google introduced this practice and analyzes its current status, after the process has been refined through decades of code changes and millions of code reviews. By means of 12 interviews, a survey with 44 respondents, and the analysis of review logs for 9 million reviewed changes, we investigate motivations behind code review at Google, current practices, and developers' satisfaction and challenges.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1145/3183519.3183525

Cites

47 of 47 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 47 references

Research works printed but not linked: 4

  1. A.F. Ackerman , P.J. Fowler , and R.G. Ebenau . 1984. Software inspections and the industrial production of software . In Symposium on Software validation: inspection-testing-verification-alternatives. A.F. Ackerman, P.J. Fowler, and R.G. Ebenau. 1984. Software inspections and the industrial production of software. In Symposium on Software validation: inspection-testing-verification-alternatives.
  2. chromium 2016. Chromium developer guidelines. https://www.chromium.org/developers/contributing-code. (August 2016 ). chromium 2016. Chromium developer guidelines. https://www.chromium.org/developers/contributing-code. (August 2016).
  3. gerrit 2016. https://www.gerritcodereview.com/. (August 2016 ). gerrit 2016. https://www.gerritcodereview.com/. (August 2016).
  4. P. Rigby B. Cleary F. Painchaud M.A. Storey and D. German. 2012. Open Source Peer Review---Lessons and Recommendations for Closed Source. IEEE Software (2012). P. Rigby B. Cleary F. Painchaud M.A. Storey and D. German. 2012. Open Source Peer Review---Lessons and Recommendations for Closed Source. IEEE Software (2012).

Cited by

See all 280

Metadata

Authors
Sadowski, C., Söderberg, E., Church, L., Sipko, M., & Bacchelli, A.
Venue
Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice
Publisher
ACM
Published
2018-05-27
Pages
181-190
OpenAlex
W2808429234
Cited by
280
References
47
FWCI
17.94
Type
conference paper
Language
en
Open access
hybrid
Funders
Swiss National Science Foundation (PP00P2_170529)

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

How to cite

Cite CoChat for the checks on this page, and the paper for its own findings.

This page
CoChat. (2026). Citation check: Modern code review: a case study at google. https://app.cochat.ai/papers/10.1145/3183519.3183525
The paper
Sadowski, C., Söderberg, E., Church, L., Sipko, M., & Bacchelli, A. (2018). Modern code review: a case study at google. Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice. https://doi.org/10.1145/3183519.3183525

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.