> You jump from Rails project to Rails project and they all work the same way. You know where everything is immediately. Except lots of projects today use very

> You jump from Rails project to Rails project and they all work the same way. You know where everything is immediately. Except lots of projects today use very diverse structures and the meat of the code is often on complex libraries like ActiveInteractors, Trailblazer Operations, stuff from the Dry-RB ecosystem, etc, or sometimes (hopefully) simple Service Pattern classes, if you're lucky. Sometimes all of them at the same time. For lots of companies, Rails projects in the real world has ceased being easy to grasp for a while.