Refactoring is the process of restructuring existing code without changing its external behaviour. Refactoring is done to improve the simplicity and readability of a piece of code. Most refactorings are simple (e.g. rename method, extract method, etc) and have been automated by modern development tools to guarantee safety/correctness. A refactoring is like renaming a section header in a document to better convey the core idea to the reader, or splitting a large, unwieldy paragraph into smaller parts.
Resource Links:
- A Guide to Naming Variables
- The Core 6 Refactorings
- Embracing the Red Bar: Safely Refactoring Tests
- Refactoring — Not on the backlog!
- What Scientific Research Has To Say About Technical Debt And Code Smells
- Workflows of Refactoring
REFACTORING BOOKS
- Refactoring: Improving the Design of Existing Code – Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts
- Refactoring to Patterns – Joshua Kerievsky
See Also:
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index
