But in this case a total rewrite would have saved time, and improved velocity. Looking back on it. It was impossible to really know at the time, though.
Fortunately this project was more presentational than business logic heavy, so missing functionality would have been easy to notice when testing (all visual).
I wouldn't agree that running is a sign of success necessarily. There are a lot of running legacy systems that get beaten out and replaced by competitors due to low development velocity.
Of course a lot of that comes down to the culture of the org and so on. But in a lot of cases architectural flaws are at the root of it.
The real question with a rewrite is a cost-benefit one. And it's based on estimates so there should be a lot of room for error.
But in this case a total rewrite would have saved time, and improved velocity. Looking back on it. It was impossible to really know at the time, though.
Fortunately this project was more presentational than business logic heavy, so missing functionality would have been easy to notice when testing (all visual).
I wouldn't agree that running is a sign of success necessarily. There are a lot of running legacy systems that get beaten out and replaced by competitors due to low development velocity.
Of course a lot of that comes down to the culture of the org and so on. But in a lot of cases architectural flaws are at the root of it.
The real question with a rewrite is a cost-benefit one. And it's based on estimates so there should be a lot of room for error.