Code review for newcomers: is it different?
Open accessThe DOI matches its Crossref record; 15 of the 15 references it cites were found in a registry or an index.
Abstract
Onboarding is a critical stage in the tenure of software developers with a project, because meaningful contribution requires familiarity with the codebase. Some software teams employ practices, such as mentoring, to help new developers get accustomed faster. Code review, i.e., the manual inspection of code changes, is an opportunity for sharing knowledge and helping with onboarding.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
Expectations, outcomes, and challenges of modern code review
Bacchelli, A., & Bird, C. (2013) · 2013 35th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2013.6606617 · Cited by 650 · cited 2×
“Manual inspection of source code changes—code review—has become a standard in modern software development [1, 2].”
BackgroundSelf-citationAn exploratory study of the pull-based software development model
Gousios, G., Pinzger, M., & Deursen, A. V. (2014) · Proceedings of the 36th International Conference on Software Engineering · doi:10.1145/2568225.2568260 · Cited by 628 · cited 2×
“[2] conducted a large-scale analysis of pull request lifecycles in GitHub projects and found that pull requests receive no special treatment and have”
BackgroundUsing Static Analysis to Find Bugs
Ayewah, N., Pugh, W., Hovemeyer, D., Morgenthaler, J. D., & Penix, J. (2008) · IEEE Software · doi:10.1109/ms.2008.130 · Cited by 534 · cited 1×
“Notable examples of automated tool support for code review include the integration of static analysis tools’ output at review time [4] and various approaches to the identification of potentially bug-introducing changes [5].”
(2013) · doi:10.5555/2486788.2486882 · Cited by 437
Self-citationToward an understanding of the motivation of open source software developers
Ye, Y., & Kishida, K. (2003) · doi:10.5555/776816.776867 · Cited by 407
Convergent contemporary software peer review practices
Rigby, P. C., & Bird, C. (2013) · Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2491411.2491444 · Cited by 311 · cited 1×
“Developers and managers responding to online questionnaries report software quality improvement as a major benefit of code review process [1], followed by a promotion of distribution of knowledge and expertise within teams [3].”
BackgroundAn examination of software engineering work practices
Singer, J., Lethbridge, T., Vinson, N., & Anquetil, N. (2010) · CASCON First Decade High Impact Papers on - CASCON '10 · doi:10.1145/1925805.1925815 · Cited by 298 · cited 1×
“tain degree of familiarity with the codebase [6].”
BackgroundThongtanunam, P., Tantithamthavorn, C., Kula, R. G., Yoshida, N., Iida, H., & Matsumoto, K.-I. (2015) · 2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER) · doi:10.1109/saner.2015.7081824 · Cited by 228 · cited 1×
“Some of the existing studies [15, 16], when focusing on open source Gerrit instances, treat the whole instance as one large project.”
BackgroundRevisiting the evaluation of defect prediction models
Mende, T., & Koschke, R. (2009) · Proceedings of the 5th International Conference on Predictor Models in Software Engineering · doi:10.1145/1540438.1540448 · Cited by 179 · cited 1×
“Notable examples of automated tool support for code review include the integration of static analysis tools’ output at review time [4] and various approaches to the identification of potentially bug-introducing changes [5].”
Do time of day and developer experience affect commit bugginess?
Eyolfson, J., Tan, L., & Lam, P. (2011) · Proceedings of the 8th Working Conference on Mining Software Repositories · doi:10.1145/1985441.1985464 · Cited by 147 · cited 1×
“bug density in their code is higher [8].”
Background
Research works printed but not linked: 5
- Bacchelli A., IEEE Press, 712
- Ye Y., IEEE, 419
- "Gerrit code review " https://www.gerritcodereview.com/ accessed: 2018-01-31. "Gerrit code review " https://www.gerritcodereview.com/ accessed: 2018-01-31.
- Hellendoorn V. J., IEEE Press, 157
- Thongtanunam P., IEEE, 141
Cited by
A systematic literature review and taxonomy of modern code review
Davila, N., & Nunes, I. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2021.110951 · Cited by 112
“Other five studies [44, 45, 46, 63, 80] conducted a similar analysis of the factors influencing the first response delay of a review request.”
BackgroundResultInfluentialWhat makes a code change easier to review: an empirical investigation on code change reviewability
Ram, A., Sawant, A. A., Castelluccio, M., & Bacchelli, A. (2018) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3236024.3236080 · Cited by 77
“Praising change authors for the positive aspects of their contribution could be beneficial irrespective of the authors’ seniority within the project, although this could be even more valuable for newcomers [59].”
BackgroundSelf-citationPull Request Decisions Explained: An Empirical Overview
Zhang, X., Yu, Y., Gousios, G., & Rastogi, A. (2022) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2022.3165056 · Cited by 94
Exploring the Capabilities of LLMs for Code-Change-Related Tasks
Fan, L., Liu, J., Liu, Z., Lo, D., Xia, X., & Li, S. (2025) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3709358 · Cited by 41
“For example, in their daily work, developers need to understand existing code changes in code repositories [18], update the comments accompanied with the changed code [22], write commit messages [49], and review the code changed by other developers [33].”
Modern Code Reviews—Survey of Literature and Practice
Badampudi, D., Unterkalmsteiner, M., & Britto, R. (2023) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3585004 · Cited by 73
Metadata
- Authors
- Kovalenko, V., & Bacchelli, A.
- Affiliations
- Delft University of Technology (NL)
- University of Zurich (CH)
- Venue
- Proceedings of the 11th International Workshop on Cooperative and Human Aspects of Software Engineering
- Publisher
- ACM
- Published
- 2018-05-27
- Pages
- 29-32
- OpenAlex
- W2811301137
- Cited by
- 18
- References
- 15
- Citations by year
- 2025: 1 · 2024: 2 · 2023: 4 · 2022: 2 · 2021: 4 · 2019: 4 · 2018: 1
- FWCI
- 1.77
- Type
- conference paper
- Language
- en
- Open access
- green
- www.zora.uzh.ch
- Locations
- International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE) (publishedVersion)
- Zurich Open Repository and Archive (University of Zurich) (acceptedVersion, other-oa)
- Data Archiving and Networked Services (DANS) (submittedVersion, other-oa)
- Research Repository (Delft University of Technology) (submittedVersion)
- Zurich Open Repository and Archive (University of Zurich) (submittedVersion, other-oa)
- Zurich Open Repository and Archive (University of Zurich)
- Funders
- SNFS (PP00P2_170529)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Computer Science Applications › Open Source Software Innovations
- Keywords
- code review, onboarding, mentoring, knowledge sharing, software development teams
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: Code review for newcomers: is it different? https://app.cochat.ai/papers/10.1145/3195836.3195842
- The paper
- Kovalenko, V., & Bacchelli, A. (2018). Code review for newcomers: is it different? Proceedings of the 11th International Workshop on Cooperative and Human Aspects of Software Engineering. https://doi.org/10.1145/3195836.3195842
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.