What Refactoring is, and what it isn’t - According to Kent Beck
and Martin Fowler CHECK OUT THE NEW REFACTORING REFCARD! --DZone
curator interruption Refactoring, as originally defined by
Martin Fowler and Kent Beck, is A change made to the internal
structure of software to make it easier to understand and
cheaper to modify without changing its observable behavior… It
is a disciplined way to clean up code that minimizes the chances
of introducing bugs. Refactoring is done to fill in short-cuts,
eliminate duplication and dead code, and to make the design and
logic clear. To make better and clearer use of the programming
language. To take advantage of information that you have now but
that the programmer didn’t have then – or that they didn’t take
advantage of then. Always to simplify the code and to make it
easier to understand. Always to make it easier and safer to
change in the future. Fixing any bugs that you find along the
way is not refactoring. Optimization is not refactoring.
Tightening up error handlin