Refactoring


Refactoring: Improving the Design of Existing Code (Addison-wesley Object Technology Series)
Refactoring to Patterns
Working Effectively with Legacy Code
Five Lines of Code: How and when to refactor
Refactoring at Scale: Regaining Control of Your Codebase
Clean Code: A Handbook of Agile Software Craftsmanship
Refactoring Databases: Evolutionary Database Design
Brutal Refactoring: More Working Effectively with Legacy Code
AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
Refactoring SQL Applications
Tidy First?: A Personal Exercise in Empirical Software Design
Head First Design Patterns
Refactoring UI
Refactoring Workbook
xUnit Test Patterns: Refactoring Test Code
Martin Fowler
People sometimes ask me what length I look for in a method. To me length is not the issue. The key is the semantic distance between the method name and the method body. If extracting improves clarity, do it, even if the name is longer than the code you have extracted.
Martin Fowler, Refactoring: Improving the Design of Existing Code

Martin Fowler
If you have to spend effort looking at a fragment of code and figuring out what it's doing, then you should extract it into a function and name the function after the "what". ...more
Martin Fowler, Refactoring: Improving the Design of Existing Code

More quotes...