kirancodes.me
To Proof Maintenance & Beyond!
FSE 2022

Understanding why we cannot model how long a code review will take: an industrial case study

Lawrence Chen, Peter C. Rigby, Nachiappan Nagappan

PDFDOI 10.1145/3540250.3558945dblp

Abstract

Code review is an effective practice for finding defects, but because it is manually intensive it can slow down the continuous integration of changes. Our goal was to understand the factors that influenced the time a change, ie a diff at Meta, would spend in review. A developer survey showed that diff reviews start to feel slow after they have been waiting for around 24 hour review. We built a review time predictor model to identify potential factors that may be causing reviews to take longer, which we could use to predict when would be the best time to nudge reviewers or to identify diff-related factors that we may need to address.

BibTeX
@inproceedings{Chen-al:FSE22,
  author    = {Lawrence Chen and
               Peter C. Rigby and
               Nachiappan Nagappan},
  title     = {Understanding why we cannot model how long a code review will take: an industrial case study},
  booktitle = {{ESEC/SIGSOFT} {FSE}},
  pages     = {1314--1319},
  publisher = {{ACM}},
  year      = {2022},
}

Related papers