February 2008
Intermediate to advanced
448 pages
9h 46m
English
Refactoring is not a new idea. I have been doing it, in one sense or another, for my entire career as a software developer, with neither a name for it nor any systematic way of describing it. I am “doing refactoring” whenever I am changing my code because I do not like how it is written, for whatever reason that is. I suspect this is true for you, too.
I have been doing refactoring in the chapters that precede this one—when I changed an example to make it more cohesive, or to decouple it, or to remove redundancy, or to make the code more readable. These were all refactorings because I was changing the code to make it better code, rather than to change its behavior.
In the year 2000, Martin ...