Not necessarily, a rewrite can just move to a language that's easier to maintain (off C / cobol).
replyHonestly though, it's pretty clear the AI rewrites work, we have a ton of high profile examples. It's just a holdover attitude about rewrites from before AI. In reality, AI is going to make the code better when it rewrites
> we have a ton of high profile examples
replySuch as?
Defining the legacy bugs and porting them as features during the rewrite is actually one of the most difficult parts of enterprise rewrites.
replyYou don't get to pick what parts of the API you're porting during something like that, it has to work the same or some of the ecosystem around it will break.
Usually you’d choose to port features in slices end to end so that you don’t have to pull in bugs as side effects. Strangler fig.
replyObviously this fails if this is a large org with many teams and microservices, but for a leaner org this isn’t really a problem.
I realize this thread is about Cisco so my comment doesn’t apply here haha.
The thing is, to get rid of unwanted behavior the first step is to document all the behavior and be able to reimplements it. Then you can pick and choose what to keep vs what to dump.
replyAnd AI is really good at all the stages here.