3 ms·
The more I read about legacy (and actively maintained) project refactoring, the more firmly I find myself agreeing that the gradual replacement is the right way
by selfhoster11 6y ago
The more I read about legacy (and actively maintained) project refactoring, the more firmly I find myself agreeing that the gradual replacement is the right way to go about things in nearly every case.
Whether we like it or not, the old system is a source of truth about how things are done, so the only way to preserve this knowledge fully is to copy the whole thing as-is and then "restate" parts of that knowledge in a more organised/modern way by refactoring, leaving the rest in place.
- steveklabnik 6y agoIf you’re interested in this topic, you should read “How to work effectively with legacy code” by Michael Feathers.
- selfhoster11 6y agoIt's been on my reading list for a while, I'll take this as a reminder to read it :)
- grey-area 6y agoThat looks really interesting, thanks for recommending it here.