Great rewrites are alomst always a bad idea. I took part in flushing 2 man-years early in my career and more recently 4 man-years. Both were rewrites that couldn't get to shore. Painful both times, moreso the 2nd time since I was one of the implementors.
It's almost always better to do small replacements. Peel the onion so-to-speak. Refactor from within first to make a migration plan away from the crufty tech possible.
First and foremost: make a plan and sell it to the devs. If you don't get buy-in from them, nothing will change.
It's almost always better to do small replacements. Peel the onion so-to-speak. Refactor from within first to make a migration plan away from the crufty tech possible.
First and foremost: make a plan and sell it to the devs. If you don't get buy-in from them, nothing will change.
Good luck.