Draft outline
This article hasn't been written yet. Below is the planned outline. Edit it in src/data/insights.ts, then set its status to published.
Planned outline
01
Why big-bang rewrites fail
- Hidden business rules in legacy code
- Feature freeze costs
- Risk concentration at cut-over
02
Assessing what you have
- Dependency and API compatibility analysis
- Identifying seams in the codebase
- Prioritizing by business value and risk
03
The strangler-fig approach in .NET
- Routing traffic with a reverse proxy
- Sharing authentication across old and new
- Migrating one vertical slice at a time
04
Protecting behavior with tests
- Characterization tests
- API contract tests
- Monitoring during migration