Harry Potter and the Legacy Codebase

on YouTube ↗28m

" summary

Claim: legacy code stores domain knowledge and yields to methodical archaeology rather than rewriting. Concrete tools and practices: use turbulence gem to chart churn vs complexity, run New Relic and benchmarks, wire tests into CI, generate maps with rails-erd and railroading. Concrete change shown: replace remove_poison with a clearer harvest_poison and extract container logic, leave deprecation warnings so tests reveal remaining callers. Outcome: small, honest refactors plus documentation and maps reduce hot spots without a full rewrite.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 0:21and The Legacy Codebase
3. 3:34LEGACY CODE ISN'T EVIL, IT'S JUST MISUNDERSTOOD
4. 7:50CODE ARCHEOLOGY 101
5. 11:54TAKE INVENTORY
6. 13:05FLAG MYTHS

" related talks

• 35mHarry Potter and The Legacy Code BaseKerri Miller · Ruby on Ales 2014
• 23mLoving Legacy CodeKeith Pitty · RubyConf AU 2015
• 39mDown The Rabbit Hole: An Adventure in Legacy CodeLoren Crawford · RailsConf 2018
• 36mWorking Compassionately with Legacy CodeAmar Shah · RubyConf 2015
• 34mTesting legacy code when you dislike tests (and legacy code)Maeve Revels · RailsConf 2022
• 09mMicrotalk:A House of Cards - The Perils of Maintaining a 7-Year-Old CodebaseJulie Gill · GoRuCo 2013
• 01h 25mGetting a Handle on Legacy CodeRandy Coulman · RailsConf 2015
• 41mTerraforming legacy Rails applicationsVladimir Dementyev · RailsConf 2019