|
|
|
|
|
|
by cncovyvysi
890 days ago
|
|
|
I found it suggests too much maintanence on the legacy system and not enough refactoring. Legacy systems shouldn't be patched with one line changes forever, you need to evolve them over time to become the modern system you want. You're never going to get "the big rewrite", or at least I'd be concerned if you did. |
|
|
I don't think this is true at all. The books starts by defining legacy systems as projects without any automated test coverage, and proceeds to dedicate virtually the whole book to focus on the problem of gradually adding tests, starting with vice tests, in a way that minimizes changes and therefore the chance of introducing regressions when refactoring code.
The whole point of the book is to help developers refactor legacy projects until they cease to be legacy projects.
If anything, the whole book is dedicated to refactoring, but following a non-trivial path that eliminates the chance of introducing regressions. It's very odd that your personal take is maintenance when none of that is covered by he book at all.