3 ms·
This is something I've struggled a bit with professionally recently. I've been leading initiatives to modernise legacy applications (both in terms of code and u
by kqr 6y ago
This is something I've struggled a bit with professionally recently. I've been leading initiatives to modernise legacy applications (both in terms of code and user experience, measurably so). This cannot be done all at once -- the applications are large and used in production and need to be maintained.
So the only option seems to be to commit to the legacy (in many ways measurably bad) implementation, or start upgrading/rewriting it a little bit at a time.
Of course, the latter is good. Except it leads to the situation you describe with multiple ongoing half-finished abstractions.
There are better ways to do it: not do all the plumbing first, and then the actual business logic, and instead do thin vertical slices at a time. But it still feels... wrong.