Legacy code,not that bad
summary
Claims that working on an 11 year e commerce codebase built with Backbone and Sass and lacking tests teaches real skills not fear it shows concrete practices used here debugging through DevTools and breakpoints rather than console logs forcing mocked data instead of waiting on backend and adding targeted comments to aid maintenance the repo proves high coupling so small changes ripple and estimated tiny tasks take days the surprising payoff is faster problem diagnosis and safer incremental refactors from tiny, careful edits no tests and tight coupling legacy code, not that bad
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:06Chaotic learning project
- 6:15Redefining legacy code
- 9:24Myths and truths about legacy
- 11:53Learning Sass in legacy
- 13:41Debugging complex systems
- 15:29Mocking data for dev
- 16:56PR feedback into growth
- 17:40Small tasks underestimated
- 18:23Thoughtful code placement
- 20:31When to comment code
- 21:55Supportive team matters
related talks
39mThe End of Legacy Code
40mMore Code More Problems
57mLiving the Best Life on a Legacy Project
31mAn Optimistic Proposal for Making Horrible Code... Bearable
30mOptimizing for Developer Delight
45m'Writing code that lasts'...or writing code you won't hate tomorrow
59mTechniques for writing high-quality code
39mClean, Concise, Collaborative Code