Hacker News Reader

Super interesting article. Is there a word for the type of software architect who pathologically excuses immediate-term problems because there is a fix a long ways away? Dr. Stroustroup's comments sound familiar if you've ever encountered the type of person who won't engage with a problem you have now, because they have a system planned for next year that makes the problem go away.

View on HN

I usually refer to this as "business oriented" - not in a derogatory sense, but because their design decisions are primarily determined by their financial impact, vs another measure (such as fault tolerance, error detection, system consistency, or projected support hours required).

A lot of business oriented people may find my delineation here offensive, but it really isn't meant to be. While a business' job is to make money, and employees work for the business, they may still disagree on how to evaluate a given action - because the business making money and being financially optimised may not be the main reason they work there.

https://en.m.wikipedia.org/wiki/Perfect_is_the_enemy_of_good

Reply on news.ycombinator.com