Editing Code refactoring (section)

==Motivation==
Refactoring is usually motivated by noticing a [[code smell]].<ref name="fowler"/> For example, the method at hand may be very long, or it may be a near [[duplicate code|duplicate]] of another nearby method. Once recognized, such problems can be addressed by ''refactoring'' the source code, or transforming it into a new form that behaves the same as before but that no longer "smells".

For a long routine, one or more smaller subroutines can be extracted; or for duplicate routines, the duplication can be removed and replaced with one shared function. Failure to perform refactoring can result in accumulating [[technical debt]]; on the other hand, refactoring is one of the primary means of repaying technical debt.<ref>{{cite book|last1=Suryanarayana|first1=Girish|title=Refactoring for Software Design Smells|date=November 2014|publisher=Morgan Kaufmann|isbn=978-0128013977|pages=258}}</ref>