Software migration
AssessTechniques
Moving a system or workload from one implementation to another, often in stages.
Why it's here
Placed in Assess: 2 article(s) of evidence from 1 source(s), led by research-stage coverage, with 2 in the last 30 days. Confidence 31%.
Evidence (2)
- 2Simon Willison·9/14/2026researchSimon Willison on influential blog posts
Simon Willison reflects on three blog posts that shaped his thinking about software engineering. He highlights Joel Spolsky’s Law of Leaky Abstractions, Will Larson’s argument for treating migrations as a core engineering skill, and Charity Majors’ Engineer/Manager Pendulum as permission to move between management and individual contributor roles.
- 3Simon Willison·9/6/2026researchWhy Big Rewrites Often Fail
Simon Willison argues that rewriting a legacy system from scratch rarely solves technical debt cleanly because the old system must keep changing while the new one is still under development. He recommends strengthening the existing system with automated tests and targeted refactors, citing migrations as a more scalable way to manage debt.