I was in a third-year group programming class in university. We were tasked with creating a web-accessible system for administrators and end users of an imagina

I was in a third-year group programming class in university. We were tasked with creating a web-accessible system for administrators and end users of an imaginary highway speed pass system. Myself and another experienced member outlined a general strategy to the group: MySQL data store wrapped by business rules enforced by a server-side component accessed via API for a PHP-based web app. Then we began outlining major classes and objects: Models for data, an API helper object. Everyone was on the same page, but for a certain "J. J.," whose contribution was: "No, we should only have four classes." "Why?" "Because we only have four kinds of users." "But we just said we'll be using an object to wrap the API —" "Yeah, that should be part of each user."