Oh, man, I've seen the damages this kind of thinking does. The Terse vs Verbose code debate is important and all, but honestly architecture is the thing that c

Oh, man, I've seen the damages this kind of thinking does. The Terse vs Verbose code debate is important and all, but honestly architecture is the thing that can make or break a project. Picking the wrong architecture for the job is the kinda thing that delays features, brings more bugs to the table and will make the exact same people ask for a rewrite down the line. I once worked on a company that was dominated by such types. They made terrible architectural decisions out of cargo-cult and it took two backend rewrites in a row to get things half-right, but they still ended up with a mongrel codebase with several mixed complex patterns. In your example, your real-life experience matters 100x more than Joe's opinion of whatever architecture he wants to use.