Microtalk:A House of Cards - The Perils of Maintaining a 7-Year-Old Codebase
summary
RoR code from 2005–2006 grows into hundreds of models and near‑billions of rows of data, with fragile meta programming and proprietary street easy magic everywhere. Setup drags in rvm homebrew mysql chef imagemagick; debugging requires git blame and tracing through views and partials. Expect to hit a 5-year-old bug last touched in 2007, to rebuild old abstractions before adding features, and to discover distant domino failures that specs sometimes catch and sometimes do not.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:13Welcome to
- 2:02Lots to Learn
- 2:25First GitHub Ticket
- 3:04Old Bugs Congrats, you found a 5-year-old bug
- 6:41Building a Feature
- 7:43Building a House of Cards
related talks
46mAncient Rails
36mWorking Compassionately with Legacy Code
26mKeeping the Rails Magic Alive After 18 Years
41mOff the Tracks - Challenging the Rails Mindset
31mAn Optimistic Proposal for Making Horrible Code... Bearable
41mExploring the History of a 12-year-old Rails Application
27mMaintainable Ruby on Rails
35mMy Rails App is Old Enough to Drink: Over Two...