RailsConf Europe 08: David Heinemeier Hansson (37signals)
summary
Claim: legacy is an opinion that inevitably appears as developers learn, not a technology failure; Rails projects age too — Basecamp spans ~5 years and still drives a business. Concrete fixes: extract a bloated application_helper 500 lines into specific modules, turn user cruft into modular concerns, move ad‑hoc boot code into initializers so environment.rb down to ~40 lines. Practice: avoid full rewrites, use Rails features (modules, before_save callbacks, partials) and always leave code you touch cleaner.
AI-written summary · about
chapters (7)
- 0:00The nature of legacy
- 4:44Growth and perception
- 10:34Choosing your outlook
- 17:43The myth of the rewrite
- 23:42The broken windows theory
- 36:14Practical refactoring
- 51:11Balancing DRY and flexibility
