Ozymandias on Rails. The Pedestal Inscription
A senior Rails engineer with 15 years of experience inside large Rails monoliths examines how successful systems become unmaintainable ruins over time. The post critiques the 'vanilla Rails is plenty' philosophy, arguing it answers the wrong question — it's scoped to small teams at a single point in time, but doesn't account for what happens when those teams grow to hundreds of engineers over a decade. Specific Rails failure modes are outlined: callbacks creating invisible control flow, ActiveRecord leaking across boundaries, polymorphic associations that can't be enforced by the database, and uncontrollable query shapes. The post argues that ownership decay compounds these structural problems — code that belongs to everyone belongs to no one. Examples from GitLab, Shopify, Gusto, and GitHub show that large Rails shops all independently built boundary tooling the framework doesn't provide. The post argues against full rewrites (citing Joel Spolsky and the second-system effect) and advocates instead for incremental recovery: tracing fires to unowned code, drawing boundaries, assigning ownership, and making implicit contracts explicit — all while the system keeps serving traffic.