How we refactor, and how we know it

By Emerson R. Murphy-Hill, Chris Parnin, Andrew P. Black. 2009 IEEE 31st International Conference on Software Engineering, 2009

709 citations recorded by the source corpus.

Subfields: Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/49acfc8071e322c0001b31ea42c51f8c12433fc9

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Networks and Communications

In Information Systems

Citations in the corpus

When and Why Your Code Starts to Smell Bad (and Whether the Smells Go Away) (2017, neutral): “[54] analyzed eight different datasets trying to understand how developers perform refactorings.”
Exploration and Explanation in Computational Notebooks (2018, neutral): “The issues of notebook “cleanliness” and intelligibility res-onate with the discussion of refactoring [8, 25] and “tech-nical debt” in software engineering.”
Accurate and Efficient Refactoring Detection in Commit History (2018, methodology): “With these additions, RMiner will be able to support the majority of the most popular refactoring types applied by developers [55, 56].”
Differential symbolic execution (2008, background): “study the practice of refactoring and provide insights into how programmers use refactoring tools and ways in which the tools can be improved to support programmer usage [50].”
The impact of tangled code changes (2013, background): “[18], [19] analyzed development activities to prove, or disprove, several common assumptions about how programmers refactor.”
Is GitHub Copilot a Substitute for Human Pair-programming? An Empirical Study (2022, background): “There have been studies on how professional developers comprehend software to understand how software development should be done, such as how programmers refactor while validating other programmers [7], and how implementation of task context for the Eclipse development environment improved productiv”
Why we refactor? confessions of GitHub contributors (2016, methodology): “Table 8 shows the most common IDEs mentioned in these answers and the percentage of refactorings performed automatically in these cases.”