4 ms·

I hate to break it to you but people do exactly this in the form of grossly over-engineered solutions with fancy design docs that impress the right people at th

• mjr00 3y ago
  That's why I said "true in some cases" Though in my 15+ year career as dev and dev manager I've only ever encountered one person who was intentionally building things poorly for job-related reasons. (Even then, that was for a company doing a federal government contract, so arguably building it in a way that encouraged expensive maintenance contracts was good for the business, in a perverse way.) I've seen a lot of overengineered solutions with fancy design docs but they've always come from a good place, genuinely thinking that the hot new tool X or architecture Y is going to solve all of the problems. I've built some poorly overengineered solutions myself. But even if that road of overengineered solutions leads to hell, it's at least paved with good intentions.
  • JohnFen 3y ago
    > Though in my 15+ year career as dev and dev manager I've only ever encountered one person who was intentionally building things poorly for job-related reasons. I agree, I've very rarely seen this done by individuals. However, I've often seen it done by teams.
  • drewcoo 3y ago
    > thinking that the hot new tool X or architecture Y is going to solve all of the problems Wanting to use X and Y and finding a way to shoehorn them into usefulness is called "motivated reasoning." Does that look any different from "coming from a good place?" Heck, it could be both motivated reasoning and coming from a good place.