Content deleted Content added
added Category:Software design patterns; removed {{uncategorized}} using HotCat |
Add author name to Five Lines of Code reference |
||
Line 4:
One use of this pattern is software rewrites. Code can be divided into many small sections, wrapped with the strangler fig pattern, then that section of old code can be swapped out with new code before moving on to the next section. This is much less risky and more incremental than swapping out the entire piece of software.<ref name=":0">{{Cite book |last=Newman |first=Sam |title=Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith |publisher=[[O'Reilly Media]] |year=2020 |isbn=978-1-492-07554-7 |pages=79–97}}</ref>
Another use of this pattern is the addition of logging to old code. For example, logging can be used to see how frequently the code is used in production, which can be used to decide whether to delete low-usage code, or to rewrite high-usage code.<ref>{{Cite book |last=Clausen |first=Christian |title=Five Lines of Code: How and when to refactor |publisher=[[Manning Publications]] |year=2021 |isbn=9781617298318 |pages=206–208}}</ref>
[[Martin Fowler (software engineer)|Martin Fowler]] created this pattern.<ref name=":0" /> Its name derives from the [[strangler fig]] plant, which tends to grow on trees and eventually kill them.
| |||