I was also using it in anger until recently, and I'm really glad I got out of it. But I disagree that it's consistent or that it leads to consistency. The "Ra

I was also using it in anger until recently, and I'm really glad I got out of it. But I disagree that it's consistent or that it leads to consistency. The "Rails way" or "DHH way" of building apps is indeed consistent, but most big teams eschew this in the name of more complicated (and less consistently applied) patterns. It follows the Anna Karenina principle to a T. All good codebases are alike and follow the Rails way; each bad codebase is bad in its own way and uses bullshit like Trailblazer, Active Interactors, over-engineered Service Objects or some other bullshit. Sometimes all of them at the same time.