Retaining and maintaining a legacy can be the right path when the external processes that interface with them are heavily laden with bureaucracies or qualificat

Retaining and maintaining a legacy can be the right path when the external processes that interface with them are heavily laden with bureaucracies or qualifications that are slow or expensive to change. Accounting is a great example, as are power plants and telecoms. But it’s important to recognize in industries with rapidly evolving standards, throwing things out can be the answer. This came back to famously bite Joel Spolsky in his defense of legacy code [1] where he argued against Netscape’s complete rewrite, which we now know today as Mozilla. [1] https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...