title: User and Account model - Whats the theory behind this?
body: <p>Today I've been reading the Rails Antipatterns book. There's a topic on page 25, where it speaks of two models: User and Account.</p>
  
  <p>The reason? Some would say data separation / separation of concerns (<a href="http://en.wikipedia.org/wiki/Separation_of_concerns" rel="nofollow">SoC</a>).</p>
  
  <p>The Account model should have stuff that isn't specific to the functionality of the user, but is related to their account. </p>
  
  <p>So for example: personal information (first_name, last_name) go into the Account model while username/ email, password etc go into the User model.</p>
  
  <p>Is this the common approach for most situations? I am trying to understand why there are two models involved. In most situations, shouldn't having a User model be enough? What is the benefit of having an Account model as well?</p>