3 ms·
That article is an incredibly useful warning against the temptation for casually taking code rewrites, but it's incomplete. Sometimes full rewrites are necessa
by InclinedPlane 15y ago
That article is an incredibly useful warning against the temptation for casually taking code rewrites, but it's incomplete.
Sometimes full rewrites are necessary and good. The trick is doing it correctly. Rewrites are riskier, more difficult, and require more development resources than greenfield development. More so when you consider that you can't just abandon the old code until the new code is mature and has proven itself.
Most people do rewrites the wrong way, and they get into trouble, but that doesn't mean there isn't a right way. There are many examples of unsuccessful rewrites in history, but also many examples of highly successful ones.