告别 Rails 惯例：序言
本文作者回顾了 16 年前开始使用 Ruby on Rails 的经历，并指出虽然 Rails 在项目初期能够加速开发，但随着项目规模的扩大和业务复杂性的增加，其固有的“惯例优先配置” (Convention over Configuration) 模式会带来诸多问题，例如代码冗余、测试缓慢、开发者对业务理解不足以及过度抽象等。
作者认为，Rails 惯例的束缚会阻碍开发者更好地处理复杂性，并呼吁 Ruby 开发者学习新的方法，如领域驱动设计 (Domain-Driven Design)，以应对大型 Rails 应用中的挑战，从而更好地应对业务需求并提升开发效率。
查看原文开头（英文 · 仅前 3 段）
In 2010, I started working with Ruby on Rails. Coming from the PHP environment, I was immediately amazed by the elegance of Ruby and how fast you can build working things with Rails. The framework took the burden of configuration off our shoulders, making it super easy and pleasant to save, validate, and pull data from the database.
16 years later, nothing really has changed. Ruby and Rails still evoke the same excitement about building a brand-new project. With the recent rise of AI, the time required to implement initial features has decreased dramatically.
The question is not whether Rails helps to build applications really fast. It helps, no doubt about it. The question is how to work with Rails as the business and team grow, with more and more features shipped every week and complexity rising.
※ 出于版权考虑，仅引用前 3 段。完整内容请阅读原文。