Blog ·
Deeper ·
·
3 min read
Continuing legacy software (without a full rewrite)
Revenue-bearing legacy isn’t thrown away for aesthetics. Stabilize it, document the critical path, evolve in slices.
By Will Fortes · Fortes Tech
“Let’s rewrite from scratch” is tempting — and expensive. Old systems often carry business rules nobody remembers until a customer complains.
A lower-risk order
- Stabilize production (backup, access, minimal monitoring).
- Map flows that make money or create risk.
- Fix the current fire.
- Extract a new module beside it (strangler) when it helps.
- Rewrite only what clearly can’t handle load or change.
Quick answers
Can you continue without the original developer?
Yes, with access and patient discovery. Without access, step one is recovering control.