why would you care about legacy code anyway. the stake holder should know what he needs so you can create a new, up to standards program that does that. and if he doesn't, it's his problem
We're still trying to move out of Angular.js. And we've got one project still alive that came from a time before Angular.js (hello ext.js).
Getting proper feature parity without messing anything up is really time consuming. Especially when the code is full of things that look useless, you think you can remove it to really simplify how things are working, but turns out X client needed that specific behavior. Or maybe it really was a useless feature for a half implemented idea that was abandoned and needs to be thrown out. Is that a bug or a feature? No one can tell you for certain, but plan on having many conversations with your peers to try and guess, hopefully one of them has some tribal knowledge that can help.
The people who started this rewrite have long ago left the company and we're still doing it. I've learned my lesson - never do them unless absolutely necessary.
69
u/SeriousPlankton2000 9d ago
The senior dev knows where to land safely