Love Letter to Legacy
summary
A migration case study of a UK tax system details lifting services from a datacenter into the cloud: a lift-and-shift of a codebase with 7 million lines and unreliable or commented-out tests, so the team adds meaningful tests, builds a feature switch to toggle old and new paths, measures planned work versus firefighting to avoid the maintenance death spiral, avoids a big‑bang rewrite, ships small replacements, and surfaces surprising issues (one commented-out encryption line yields remote code execution).
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:10Legacy code defined
- 3:20Lifting legacy to cloud
- 7:38Legacy value and stability
- 10:10Death spiral of legacy
- 11:36Improving legacy systems
- 12:40Debunking the myth of legacy as purely negative
- 14:28Experience with legacy
- 16:37Team for legacy work
- 19:51Great legacy team
- 20:14Big bang pitfalls
- 21:59Legacy teaches you
- 24:54Measuring legacy success
- 25:39Final advice
related talks
20mLegacy Migration... Differently
47mLegacy Software: Really a Problem?
41mLegacy, for lack of a better word, is good
48mLegacy, for lack of a better word, is good
18mUnlocking Value from Legacy Technology
44mLegacy Software Really a Problem
41mModernizing Legacy Apps - Platforms and Strategies
23mDevOps and Legacy Code