mlsanityData to 7 Oct 2026

Why We Refactor? Confessions of GitHub Contributors

arXiv 1607.02459 ↗First posted 8 Jul 2016cs.SEcited by 10

Not on the map. Why?

Abstract (arXiv)

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 ex- plain 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.

Key facts. Cited by 10 papers in the map (data through 7 Oct 2026). First posted on arXiv 8 Jul 2016.

Builds on

No reference list yet.

Built on by

Cited by year (2026 to 7 Oct)

Citing papers per year: 2023: 1; 2024: 1; 2025: 7; 2026: 1.

10 papers.