Applications are built for users. We give them distinguishing properties, connect them to other entities, respond to their actions, and make various decisions based on any combination of those things.
In rails, it's almost guaranteed that sitting inside of app/models/
is a class called User
. I'm sure you're intimately familiar with this class. In fact, I suspect that if you were to hack together a heat-map representing your code editor, user.rb
would probably be molten.
Taking this into consideration, how would you describe the responsibility of your User
model? I've noticed a few trends while working in rails: