These are all remedies for the symptoms. The actual disease, which is considering the framework part of your core business application, remains. Decoupling fro

These are all remedies for the symptoms. The actual disease, which is considering the framework part of your core business application, remains. Decoupling from your persistence (and presentation, fwiw) brings a lot of benefits, not only faster tests. I'm sick of people saying "why introduce a layer here if we'll never change the database?". The answer is simple: yes, you will change the database, specially when testing where you want to plug an in-memory store. Again, I get that Rails gives us conventions so we don't keep bikeshedding, but how often do we challenge these conventions? How often do we question whether the problem we're solving fits the CRUD/MVC patterns?