This article is valuable since it's raising some interesting pitfalls it's good to know and avoid. That being said: you need to use the right tool for the job.

This article is valuable since it's raising some interesting pitfalls it's good to know and avoid. That being said: you need to use the right tool for the job. It's just hilarious how people expect the new "foo framework/paradigm" to solve ALL the problems... jeez! It's nice to know and understand new paradigms, but you really need to evaluate your case. ORMs took away the complexity of 90% of web apps. All the "Model X has many model Y". If you step outside of that realm with the ORM then you're officially "fighting the framework", and bad things will happen.