Refactoring - Design improvement
Because XP doctrine advocates programming only what is needed today, and implementing it as simply as possible,
at times this may result in a system that is stuck. One of the symptoms of this is the need for dual (or multiple) maintenance:
functional changes start requiring changes to multiple copies of the same (or similar) code. Another symptom is that changes
in one part of the code affect lots of other parts. XP doctrine says that when this occurs, the system is telling you to refactor
your code by changing the architecture, making it simpler and more generic.
Code refactoring is the process of changing a computer program's source code without modifying its external functional behavior
in order to improve some of the nonfunctional attributes of the software.
Advantages include improved code readability and reduced complexity to improve the maintainability of the source code,
as well as a more expressive internal architecture or object model to improve extensibility.
"By continuously improving the design of code, we make it easier and easier to work with.
This is in sharp contrast to what typically happens: little refactoring and a great deal of attention paid to
expediently adding new features. If you get into the hygienic habit of refactoring continuously, you'll find
that it is easier to extend and maintain code."
We would like to suggest you the following list of usefull resources on the topic: