All notes
You probably don’t need a rewrite
A practical test for deciding between rewriting a legacy system and evolving it in place.
Every few years a team looks at its oldest system and decides the only way forward is to start again. Sometimes that’s right. Usually it isn’t.
Three questions to ask first
- Can you describe what the system does, completely? If not, a rewrite will rediscover every edge case the hard way, in production.
- Can the business pause feature work for the duration? If not, you’ll be building two systems at once.
- Is the pain in the code, or in how the code is deployed and tested? Surprisingly often, it’s the second.
If you answered “no, no, deployment”, an incremental approach will almost certainly get you further, faster.
Placeholder article. Replace with your own writing.