The End of Legacy Code
summary
Argues that “legacy code” is solvable by an Eternal Onboarding mindset and concrete practices not rhetoric: inventoryed app setup, onboarding docs, factories (FactoryBot), tests, pairing, Git history and JetBrains tools; cites a 14‑year Rails app with a two‑year React front end as a worked example and notes many Rails apps are over a decade old; recommends pay it forward investments and leaving Trail Markers so newcomers boot, reproduce bugs, and ship features without fear, and reports that these steps measurably reduce friction.
AI-written summary · about
chapters (4)
related talks
48mThree Principles To Bring Your Legacy Code Into the Future
50mWe ♥️ legacy
42mKeynote - Livable Code
23mLegacy code,not that bad
57mLiving the Best Life on a Legacy Project
22mHow to write better legacy code: A developer's wishlist
57mCtrl-Alt-Del: Learning to Love Legacy Code
41mCreating A Better Developer Experience By Avoiding Legacy Code
