Resources to help guide architectural decisions in Rails apps

My previous post outlined a trivial example where I refactored some basic, boring business logic into a service object, or transaction script (depending on who you ask). It set off a lot of debate on Twitter and Hacker news about the topic. I was quite surprised. At the very least it means that many others have felt the pain of having rails dictate your applications core architecture. »

Where the logic hides in Rails apps

DHH recently authored a SVN blog post that advocated breaking up fat models into separate mixins that would live in a new directory in the rails structure, app/concerns. He made it clear that breaking up domain logic into concerns will make code easier »