Editing Code refactoring (section)

==Benefits==
There are two general categories of benefits to the activity of refactoring.
# [[Maintainability]]. It is easier to fix bugs because the source code is easy to read and the intent of its author is easy to grasp.<ref name=martin>{{cite book | last = Martin | first = Robert |title = Clean Code | publisher = Prentice Hall | year = 2009}}</ref> This might be achieved by reducing large monolithic routines into a set of individually concise, well-named, single-purpose methods. It might be achieved by moving a method to a more appropriate class, or by removing misleading comments.
# [[Extensibility]]. It is easier to extend the capabilities of the application if it uses recognizable [[design pattern (computer science)|design patterns]], and it provides some flexibility where none before may have existed.<ref name=kerievsky/>
Performance engineering can remove inefficiencies in programs, known as software bloat, arising from traditional software-development strategies that aim to minimize an application's development time rather than the time it takes to run. Performance engineering can also tailor [[software]] to the [[Hardware security module|hardware]] on which it runs, for example, to take advantage of parallel processors and vector units.<ref>{{Cite journal|doi=10.1126/science.aam9744|doi-access=free|title=There's plenty of room at the Top: What will drive computer performance after Moore's law?|year=2020|last1=Leiserson|first1=Charles E.|last2=Thompson|first2=Neil C.|last3=Emer|first3=Joel S.|last4=Kuszmaul|first4=Bradley C.|last5=Lampson|first5=Butler W.|last6=Sanchez|first6=Daniel|last7=Schardl|first7=Tao B.|journal=Science|volume=368|issue=6495|pages=eaam9744|pmid=32499413}}</ref>