What the article describes is a rewrite! In the end there will be no more legacy code left... What the article is saying is: don’t rewrite your code in one g

What the article describes is a rewrite! In the end there will be no more legacy code left... What the article is saying is: don’t rewrite your code in one go, but rather cut the system in pieces that are independent and rewrite each in successive phases. It’s kind of obvious, though. And the difficult part of the rewrite is actually to slice the original code in indépendant chunks. More often than not legacy systems are riddle with leaky abstractions and dependencies (the infamous spaghetti code), that’s a hell to disentangle.