How we refactor, and how we know it
The DOI matches its Crossref record; 20 of the 20 references it cites were found in a registry or an index.
Abstract
Much of what we know about how programmers refactor in the wild is based on studies that examine just a few software projects. Researchers have rarely taken the time to replicate these studies in other contexts or to examine the assumptions on which they are based. To help put refactoring research on a sound scientific basis, we draw conclusions using four data sets spanning more than 13 000 developers, 240 000 tool-assisted refactorings, 2500 developer hours, and 3400 version control commits. Using these data, we cast doubt on several previously stated assumptions about how programmers refactor, while validating others. For example, we find that programmers frequently do not indicate refactoring activity in commit logs, which contradicts assumptions made by several previous researchers. In contrast, we were able to confirm the assumption that programmers do frequently intersperse refactoring with other program changes. By confirming assumptions and replicating studies made by other researchers, we can have greater confidence that those researchers' conclusions are generalizable.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
Refactoring: Improving the Design of Existing Code
Fowler, M. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45672-4_31 · Cited by 5,591
Refactoring improving the design of existing code
Saca, M. A. (2017) · 2017 IEEE 37th Central America and Panama Convention (CONCAPAN XXXVII) · doi:10.1109/concapan.2017.8278488 · Cited by 2,054
How are Java software developers using the Eclipse IDE?
Murphy, G. C., Kersten, M., & Findlater, L. (2006) · IEEE Software · doi:10.1109/ms.2006.105 · Cited by 413 · cited 1×
“The first set we will call Users; it was originally collected in the latter half of 2005 by Murphy and colleagues [7], who used the Mylyn Monitor tool to capture and analyze fine-grained usage data from 41 volunteer programmers in the wild using the Eclipse development environment (http://eclipse.”
MethodAutomated Detection of Refactorings in Evolving Components
Dig, D., Comertoglu, C., Marinov, D., & Johnson, R. (2006) · Lecture Notes in Computer Science · doi:10.1007/11785477_24 · Cited by 251 · cited 2×
“For example, several researchers have used automatic refactoringdetection tools to find refactorings in version histories, but these tools can generally detect only those refactorings that modify packages, classes, and member signatures [3, 4, 18, 19].”
BackgroundMethodPreprocessing CVS data for fine-grained analysis
Zimmermann, T. (2004) · "International Workshop on Mining Software Repositories (MSR 2004)" W17S Workshop - 26th International Conference on Software Engineering · doi:10.1049/ic:20040466 · Cited by 214 · cited 1×
“The standard approach for recovering transactions is to find revisions committed by the same developer with the same commit message within a small time window [22]; we use a 60 second time window.”
MethodWhat do large commits tell us?: a taxonomical study of large commits
Hindle, A., German, D. M., & Holt, R. (2008) · Proceedings of the 2008 international working conference on Mining software repositories · doi:10.1145/1370750.1370773 · Cited by 204 · cited 2×
“It also casts doubt on previous research that relies on this technique [6, 13, 15].”
BackgroundResultRefactoring--Does It Improve Software Quality?
Stroggylos, K., & Spinellis, D. (2007) · Fifth International Workshop on Software Quality (WoSQ'07: ICSE Workshops 2007) · doi:10.1109/wosq.2007.11 · Cited by 159 · cited 1×
“Murphy and colleagues originally used these data to characterize the way programmers used Eclipse, including a coarse-grained analysis of which refactoring tools were used most often.”
MethodRefactoring Tools: Fitness for Purpose
Murphy-Hill, E., & Black, A. P. (2008) · IEEE Software · doi:10.1109/ms.2008.123 · Cited by 155 · cited 9×
“9) confirm the results of our survey on programmers’ under-use of refactoring tools [10].”
BackgroundResultInfluentialSelf-citationBreaking the barriers to successful refactoring: observations and tools for extract method
Murphy-Hill, E., & Black, A. P. (2008) · Proceedings of the 13th international conference on Software engineering - ICSE '08 · doi:10.1145/1368088.1368146 · Cited by 129 · cited 1×
“We have observed that programmers occasionally initiate a refactoring tool on some code, cancel the refactoring, and then re-initiate the same refactoring shortly thereafter [9].”
BackgroundSelf-citationOn the relation of refactorings and software defect prediction
Ratzinger, J., Sigmund, T., & Gall, H. C. (2008) · Proceedings of the 2008 international working conference on Mining software repositories · doi:10.1145/1370750.1370759 · Cited by 119
Cited by
How We Refactor, and How We Know It
Murphy-Hill, E., Parnin, C., & Black, A. P. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.41 · Cited by 547
Self-citationThe impact of tangled code changes
Herzig, K., & Zeller, A. (2013) · 2013 10th Working Conference on Mining Software Repositories (MSR) · doi:10.1109/msr.2013.6624018 · Cited by 270
(2012) · doi:10.1145/2393596.2393655 · Cited by 239
An Empirical Study of RefactoringChallenges and Benefits at Microsoft
Kim, M., Zimmermann, T., & Nagappan, N. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2318734 · Cited by 231
“and programmers do not leverage them as effectively as they could [38].”
BackgroundOn the Relevance of Code Anomalies for Identifying Architecture Degradation Symptoms
Macia, I., Arcoverde, R., Garcia, A., Chavez, C., & von Staa, A. (2012) · 2012 16th European Conference on Software Maintenance and Reengineering · doi:10.1109/csmr.2012.35 · Cited by 121
“There is also no work that investigates to what extent the adopted refactoring strategies are able to remove architecturally-relevant code anomalies.”
BackgroundMethodAn Information Foraging Theory Perspective on Tools for Debugging, Refactoring, and Reuse Tasks
Fleming, S. D., Scaffidi, C., Piorkowski, D., Burnett, M., Bellamy, R., Lawrance, J., & Kwan, I. (2013) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/2430545.2430551 · Cited by 79
Improving software developers' fluency by recommending development environment commands
Murphy-Hill, E., Jiresal, R., & Murphy, G. C. (2012) · Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering · doi:10.1145/2393596.2393645 · Cited by 67
Self-citationThe Influence of the Task on Programmer Behaviour
Ying, A. T. T., & Robillard, M. P. (2011) · 2011 IEEE 19th International Conference on Program Comprehension · doi:10.1109/icpc.2011.35 · Cited by 41
“, to understand how developers refactor [6].”
Software Architecture in Practice: Challenges and Opportunities
Wan, Z., Zhang, Y., Xia, X., Jiang, Y., & Lo, D. (2023) · Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3611643.3616367 · Cited by 30
“The difficulty in such activities manifests itself in a variety of ways, e.g., increased cost, complex implementation, and highly scattered code changes.”
BackgroundDetecting architecturally-relevant code smells in evolving software systems
Bertran, I. M. (2011) · Proceedings of the 33rd International Conference on Software Engineering · doi:10.1145/1985793.1986003 · Cited by 28
“We have observed that long-life smells [11] are often related to architecture degeneration (e.g. Composition Bloat [8]).”
Background
Metadata
- Authors
- Murphy-Hill, E., Parnin, C., & Black, A. P.
- Venue
- 2009 IEEE 31st International Conference on Software Engineering
- Publisher
- IEEE
- Published
- 2009
- Pages
- 287-297
- OpenAlex
- W2098664130
- Cited by
- 197
- References
- 20
- FWCI
- 14.94
- Type
- conference paper
- Language
- en
- Open access
- closed
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
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.