Editing Code refactoring (section)

==Timing and responsibility==
There are two possible times for refactoring.
# Preventive refactoring – the original developer of the code makes the code more robust when it is still free of [[Code smell|smells]] to prevent the formation of smells in the future.<ref name="fraivert2022">
{{Cite conference
|last1=Fraivert|first1=Dov
|last2=Lorenz|first2=David H.
|title=Language Support for Refactorability Decay Prevention
|date=2022
|book-title=Proceedings of the 21st ACM SIGPLAN International Conference on Generative Programming: Concepts and Experiences
|pages=122–134
|doi=10.1145/3564719.3568688
|isbn=978-1-4503-9920-3
}}</ref>
# Corrective refactoring – a subsequent developer performs refactoring to correct [[code smell]]s as they occur.<ref name="fraivert2022" />

A method that balances preventive and corrective refactoring is "shared responsibility for refactoring".
This approach splits the refactoring action into two stages and two
roles. The original developer of the code just prepares the code for refactoring, and when the [[code smell]]s form, a subsequent developer carries out the actual refactoring action.<ref name="fraivert2022" />