The monster under the bed - working with legacy code
summary
Argues that legacy code can be an asset and lays out a practical migration path: add tests (unit and integration), wrap functionality with APIs, split a monolith into smaller front ends, and use feature switching to deploy safely. Recommends incremental work — one pull request at a time — and keeping new code clean. Describes replacing a Classic ASP store with APIs and parallel frontends that enable independent releases, translations, and gradual retirement of the old system.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:10Different cultures
- 0:28folklore
- 1:07introduction
- 1:37what is legacy code
- 2:20all code becomes legacy code
- 2:41a different message
- 3:33attitude
- 4:17practical aspects
- 6:55company history
- 8:37what worked
related talks
46mHow to escape Legacy Hell
01mThe Path Through Legacy: Delicate Balance Between Tolerance and Phobia
32mLegacy Code: Big Rewrite or Progressive Rejuvenation?
45mChanging attitudes toward legacy code
01h 00mOld to Gold: How to Modernize Your Legacy ASP.NET Apps Gradually
41mRefactoring your legacy applications the right way
45mHitchhiker’s Guide for Software Architects: Legacy Migration
45mHow we rebuild a legacy monolithic platform at CERN and still sleep at night
