Five reasons you shouldn’t rewrite that code

Before you commit to rewriting an old system, here are some reasons it’s (almost always) a bad idea.

Here’s a common challenge for engineering leaders:

The team they are managing is frustrated. They are struggling to ship features, and they complain that the issue is that the old systems are just too hard to work in. These systems are written in a legacy programming language that no one likes, the original builders made bad architectural choices that just won’t scale, or everything is just far too brittle, and every change takes too long to test and still fails half the time.

Join LeadDev.com for free to access this content