I'm an old dog. If I'm honest, Rails is the only thing I know (... I barely know a lot of things).
Counter do DHH's and core Rails' pattern, I'm thin models and Service Objects (GASP the horror!) to handle business logic. Models become DAO-y.
I had a lot of mental trouble handling different use cases for the same object. Like if an Admin vs User updates a post. The notification chains are completely different. So now my service objects look like: Post::UpdateByAdmin < Post::Base vs Post::UpdateByUser < Post::Base.
So, in general, my concerns are pretty thin. Like the post only handle data grabs. Even then, I'm guilty of doing what the post says from time to time especially when I couldn't see far enough into the future.
Counter do DHH's and core Rails' pattern, I'm thin models and Service Objects (GASP the horror!) to handle business logic. Models become DAO-y.
I had a lot of mental trouble handling different use cases for the same object. Like if an Admin vs User updates a post. The notification chains are completely different. So now my service objects look like: Post::UpdateByAdmin < Post::Base vs Post::UpdateByUser < Post::Base.
So, in general, my concerns are pretty thin. Like the post only handle data grabs. Even then, I'm guilty of doing what the post says from time to time especially when I couldn't see far enough into the future.