Ctrl-Alt-Del: Learning to Love Legacy Code
summary
Worked on the same Spotlight codebase from 2000–2018 and shows concrete techniques that let teams change legacy systems safely: run a local copy of the database, redirect external APIs with the hosts file loopback and serve canned JSON, beware message queues, and use a continuous deployment tracer bullet (add a “verified” comment to a page to prove the release path). Defines legacy as too scary to update and too profitable to delete, and gives the DB-width-to-256-chars experiment as an example of validation.
AI-written summary · about
chapters (40)
- 0:00First Time
- 8:35Somethings Coming
- 10:46Introduction
- 11:18Spotlight
- 13:41Rate of change
- 15:53Nostalgia
- 16:53Legacy Code
- 17:11How Legacy is this
- 17:34The Legacy Codeometer
- 17:55What is Legacy Code
- 18:30Wikipedia
- 19:19Michael Feathers
- 19:43Legacy Code Definition
- 21:08Double Entry Bookkeeping
- 22:25Why you shouldnt interrupt
- 22:58The mental model
- 24:25Downhill invention
- 25:07The Dungeon Master
- 26:30Code that already exists
- 28:11Why MDC
- 28:46Resume
- 29:00The Message
- 30:24Trust
- 32:43Computer Science Education
- 34:03Learning in a Hurry
- 34:51How Many Words
- 35:19Comparative Analysis
- 36:15The Linux Kernel
- 37:20Richard Feynman
- 39:02The Scientific Method
- 41:03Sandbox Environments
- 44:06Continuous Deployment
- 46:02Classic ASP
- 47:02Legacy Code Fear of Change
- 48:14Star Trek The Next Generation
- 49:48Collective Responsibility
- 52:06Keeping Track
- 54:01Done
- 54:30Confidence
- 54:53Conclusion
related talks
50mWe ♥️ legacy
39mThe End of Legacy Code
22mHow to write better legacy code: A developer's wishlist
53mTools and practices to help you deal with legacy code
48mThree Principles To Bring Your Legacy Code Into the Future
35mQuickly and Safely Refactoring Legacy Code
57mLiving the Best Life on a Legacy Project
35mRedundancy Driven Development - Navigating disruptive codebase changes.