It works, but every change is a risk
A codebase only one or two people understand, releases that are slow and fragile, workarounds piling up, and new developers who take months to get going.
- Find where the complexity and risk really are
- Restructure, or rebuild the parts that can't be saved, without stopping the business
- Proper testing, deployment and release processes
Track recordLegacy desktop software rebuilt for the web, legacy C rewritten, and production applications taken over from other teams.
Legacy rewrite →