The DOI matches its Crossref record; 36 of the 36 references it cites were found in a registry or an index.
Why we refactor? confessions of GitHub contributors
Open accessAbstract
Refactoring is a widespread practice that helps developers to improve the maintainability and readability of their code. However, there is a limited number of studies empirically investigating the actual motivations behind specific refactoring operations applied by developers. To fill this gap, we monitored Java projects hosted on GitHub to detect recently applied refactorings, and asked the developers to explain the reasons behind their decision to refactor the code. By applying thematic analysis on the collected responses, we compiled a catalogue of 44 distinct motivations for 12 well-known refactoring types. We found that refactoring activity is mainly driven by changes in the requirements and much less by code smells. Extract Method is the most versatile refactoring operation serving 11 different purposes. Finally, we found evidence that the IDE used by the developers affects the adoption of automated refactoring tools.
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
Extreme Programming Explained: Embrace Change
Beck, K. L., & Andres, C. (2000) · Cited by 5,902
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
Violin Plots: A Box Plot-Density Trace Synergism
Hintze, J. L., & Nelson, R. D. (1998) · The American Statistician · doi:10.1080/00031305.1998.10480559 · Cited by 1,802
A survey of software refactoring
Mens, T., & Tourwe, T. (2004) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2004.1265817 · Cited by 1,193
Recommended Steps for Thematic Synthesis in Software Engineering
Cruzes, D. S., & Dyba, T. (2011) · 2011 International Symposium on Empirical Software Engineering and Measurement · doi:10.1109/esem.2011.36 · Cited by 960
Feature location in source code: a taxonomy and survey
Dit, B., Revelle, M., Gethers, M., & Poshyvanyk, D. (2013) · Journal of Software: Evolution and Process · doi:10.1002/smr.567 · Cited by 583
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
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
Recommendation Systems for Software Engineering
Robillard, M., Walker, R., & Zimmermann, T. (2010) · IEEE Software · doi:10.1109/ms.2009.161 · Cited by 388
UMLDiff: an algorithm for object-oriented design differencing
Xing, Z., & Stroulia, E. (2005) · Proceedings of the 20th IEEE/ACM International Conference on Automated Software Engineering · doi:10.1145/1101908.1101919 · Cited by 374
Identification of Move Method Refactoring Opportunities
Tsantalis, N., & Chatzigeorgiou, A. (2009) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2009.1 · Cited by 339
Self-citation(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
Template-based reconstruction of complex refactorings
Prete, K., Rachatasumrit, N., Sudan, N., & Kim, M. (2010) · 2010 IEEE International Conference on Software Maintenance · doi:10.1109/icsm.2010.5609577 · Cited by 202
Methodbook: Recommending Move Method Refactorings via Relational Topic Models
Bavota, G., Oliveto, R., Gethers, M., Poshyvanyk, D., & Lucia, A. D. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2013.60 · Cited by 172
Non-essential changes in version histories
Kawrykow, D., & Robillard, M. P. (2011) · Proceedings of the 33rd International Conference on Software Engineering · doi:10.1145/1985793.1985842 · Cited by 169
Identification of extract method refactoring opportunities for the decomposition of methods
Tsantalis, N., & Chatzigeorgiou, A. (2011) · Journal of Systems and Software · doi:10.1016/j.jss.2011.05.016 · Cited by 168
Self-citationSoftware Engineering Data Collection for Field Studies
Singer, J., Sim, S. E., & Lethbridge, T. C. (2007) · Springer eBooks · doi:10.1007/978-1-84800-044-5_1 · Cited by 167
A Comparative Study of Manual and Automated Refactorings
Negara, S., Chen, N., Vakilian, M., Johnson, R. E., & Dig, D. (2013) · Lecture notes in computer science · doi:10.1007/978-3-642-39038-8_23 · Cited by 157
Untangling fine-grained code changes
Dias, M., Bacchelli, A., Gousios, G., Cassou, D., & Ducasse, S. (2015) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2015.7081844 · Cited by 153
An empirical investigation into the role of API-level refactorings during software evolution
Kim, M., Cai, D., & Kim, S. (2011) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1985793.1985815 · Cited by 140
Mining fine-grained code changes to detect unknown change patterns
Negara, S., Codoban, M., Dig, D., & Johnson, R. E. (2014) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/2568225.2568317 · Cited by 129
Breaking the barriers to successful refactoring
Murphy-Hill, E. R., & Black, A. P. (2008) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1368088.1368146 · Cited by 129
Identifying Extract Class refactoring opportunities using structural and semantic cohesion measures
Bavota, G., Lucia, A. D., & Oliveto, R. (2010) · Journal of Systems and Software · doi:10.1016/j.jss.2010.11.918 · Cited by 126
Assessing the Refactorability of Software Clones
Tsantalis, N., Mazinanian, D., & Krishnan, G. P. (2015) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2015.2448531 · Cited by 105
Self-citationAre refactorings less error-prone than other changes?
Weißgerber, P., & Diehl, S. (2006) · International Conference on Mining Software Repositories (MSR) · doi:10.1145/1137983.1138011 · Cited by 99
Increasing clone maintenance support by unifying clone detection and refactoring activities
Tairas, R., & Gray, J. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2012.06.011 · Cited by 80
Recommending Refactoring Operations in Large Software Systems
Bavota, G., Lucia, A. D., Marcus, A., & Oliveto, R. (2013) · Springer eBooks · doi:10.1007/978-3-642-45135-5_15 · Cited by 75
Recommending automated extract method refactorings
Silva, D., Terra, R., & Valente, M. T. (2014) · International Conference on Program Comprehension · doi:10.1145/2597008.2597141 · Cited by 74
Self-citationA multidimensional empirical study on refactoring activity
Tsantalis, N., Guana, V., Stroulia, E., & Hindle, A. (2013) · Conference of the Centre for Advanced Studies on Collaborative Research · Cited by 71
Self-citationThe Design Space of Bug Fixes and How Developers Navigate It
Murphy-Hill, E. R., Zimmermann, T., Bird, C., & Nagappan, N. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2357438 · Cited by 68
Recommending Move Method refactorings using dependency sets
Sales, V., Terra, R., Miranda, L. F., & Valente, M. T. (2013) · Working Conference on Reverse Engineering (WCRE) · doi:10.1109/wcre.2013.6671298 · Cited by 68
Self-citationComparing approaches to analyze refactoring activity on software repositories
Soares, G., Gheyi, R., Murphy-Hill, E. R., & Johnson, B. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2012.10.040 · Cited by 48
Does Automated Refactoring Obviate Systematic Editing?
Meng, N., Hua, L., Kim, M., & McKinley, K. S. (2016) · Cited by 41
Does the "Refactor to Understand" Reverse Engineering Pattern Improve Program Comprehension?
Bois, B. D., Demeyer, S., & Verelst, J. (2005) · Euromicro Conference on Software Maintenance and Reengineering (CSMR) · doi:10.1109/csmr.2005.25 · Cited by 40
What motivate software engineers to refactor source code? evidences from professional developers
Yi, W. (2009) · Proceedings/Proceedings - Conference on Software Maintenance · doi:10.1109/icsm.2009.5306290 · Cited by 33
Cited by
Accurate and efficient refactoring detection in commit history
Tsantalis, N., Mansouri, M., Eshkevari, L. M., Mazinanian, D., & Dig, D. (2018) · Proceedings of the 40th International Conference on Software Engineering · doi:10.1145/3180155.3180206 · Cited by 300
Self-citationChatGPT: A Study on its Utility for Ubiquitous Software Engineering Tasks
Sridhara, G., G., R. H., & Mazumdar, S. (2023) · arXiv · doi:10.48550/arxiv.2305.16837 · Cited by 68
“Background: Code refactoring is a software maintenance activity in which developers modify the code to make it more readable and hence increase maintainability [Silva et al.(2016)].”
PYEVOLVE: Automating Frequent Code Changes in Python ML Systems
Dilhara, M., Dig, D., & Ketkar, A. (2023) · 2023 IEEE/ACM 45th International Conference on Software Engineering (ICSE) · doi:10.1109/icse48619.2023.00091 · Cited by 46
“Thus, they will appeal to developers who might not like hard-coded refactoring tools that automate code changes [45], [84] without any intervention from the developer.”
BackgroundIndustry experiences with large-scale refactoring
Ivers, J., Nord, R. L., Ozkaya, I., Seifried, C., Timperley, C. S., & Kessentini, M. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3558954 · Cited by 19
“Furthermore, studies analyzing GitHub contributions reveal that refactorings are driven more often by changing requirements than by code smells [34].”
Background
Metadata
- Authors
- Silva, D., Tsantalis, N., & Valente, M. T.
- Venue
- Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2016-11
- Pages
- 858-870
- OpenAlex
- W2476494490
- Cited by
- 280
- References
- 36
- FWCI
- 20.80
- Type
- conference paper
- Language
- en
- Open access
- green
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.