
Refactor versus rewrite legacy code

Working Effectively with Legacy Code and AI Coding Assistant - Michael Feathers
Topic 4 of 22
Published Oct 14, 2024 · Clip 13:51–15:37 (1:46)
Michael explains that rewrite decisions come down to business reasons rather than technical ones: you rarely need to rewrite an entire system, and should concentrate on areas with future growth and current difficulty. He advocates spot rewrites over all-or-nothing approaches and notes that rewrites are great if you have tests, but without tests you now have two problems. He distinguishes rewrites for technical debt from larger architecture-driven rewrites with different considerations.