Closing Keynote
summary
Argues that modular monoliths organized with Rails engines and enforced by Packwork don't magically fix the real problems and often introduce new ones: Shopify reports about 40 top‑level contexts and over 90 package to‑do files, yet no component is deployed in isolation and the core monolith remains the oldest continuously developed production Rails application now running on Rails Edge. Highlights concrete anti patterns like primitive obsession, ownership silos, duplicated code, circular deps, flaky CI and slow deploys, and prescribes developer education, indoctrination into Rails practices, and leadership that rewards maintenance.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:58Monoliths turn to mud
- 12:03Myth of modular monolith
- 21:47Modularization problems
- 32:04Human problems cannot be solved by architecture
- 41:30Fixing culture not silver bullets
- 44:58Call to action
related talks
17mDesigning software that maximizes developer productivity
41mWriting Modular Ruby Code: Lessons Learned from Rails 3
34mShitlist-driven development and other tricks for working on large codebases
32mComponent-based Architectures in Ruby and Rails
01h 00mKeynote: Why Ruby?
09m"What's Missing?"
26mDon't Call It a Comeback
29mOn Second Acts