Sustainable Architecture
summary
Argues that database-driven development causes bugs like balances breaking when migrations re-run callbacks and that 10–20 nested callbacks create real maintenance pain; recommends separating persistence (ActiveRecord/Sequel/ActiveModel) from business logic, moving CSV/XML/webhook formatting out of controllers, and grouping code into bounded contexts so features change in one place. Practical steps: use git/SCM heatmaps to find the most-changed complex files, add tests, incrementally refactor god classes into smaller cohesive objects, apply dependency inversion, and prefer buying small framework pieces over wholesale rewrites.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:59Why sustainable architecture matters
- 8:22Database driven development pitfalls
- 12:16Separating persistence from logic
- 16:55Growing features without complexity
- 21:10Applying design principles
- 26:30Managing system complexity
- 29:19Q&A session
related talks
38mAgile Architecture
50mTowards an Evolutionary Architecture
28mAvoid overengineering & big ball of mud- 7 lessons for maintaining the balance
36m"Business Logic in Ruby"
32mKeeping your code strong
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 01mClean Architecture
44mThe Art of Architecting for Scale