Do you ever break up a large rails model class into smaller classes for
sake of just having smaller classes?
I have a user model class that is growing in number of attributes quite
quickly. A part of me thinks I should group attributes together and
them off as separate classes in order to reduce the number of attributes
the user class, another part of me says that the extra work to create
maintain a separate table plus the has-one/belongs_to relationship makes
so doing this just isn’t worth it. I don’t have any problems using this
class, it’s just the growing number of attributes and instance methods
approaching 50, and it just smells funny.
Do you do anything about this?