Following the rant of: <a href="http://blog.steveklabnik.com/posts/2011-12-30-active-record-considered-harmful" rel="nofollow">http://blog.steveklabnik.com/posts/2011-12-30-active-record-...</a>
And the not very classy reply of: <a href="http://news.ycombinator.com/item?id=3418601" rel="nofollow">http://news.ycombinator.com/item?id=3418601</a><p>I think this article provide a nice explanation on why rails best practices are not that bad for the use cases it was designed for. It also suggests to move away from them, evolving an app architecture when it becomes more complex.