title: Data validation: fail fast, fail early vs. complete validation
body: <p>Regarding data validation, I've heard that the options are to "fail fast, fail early" or "complete validation". The first approach fails on the very first validation error, whereas the second one builds up a list of failures and presents it.</p>
  
  <p>I'm wondering about this in the context of both server-side and client-side data validation. Which method is appropriate in what context, and why?</p>
  
  <p>My personal preference for data-validation on the client-side is the second method which informs the user of all failing constraints. I'm not informed enough to have an opinion about the server-side, although I would imagine it depends on the business logic involved.</p>