Hacker News Reader

Comment by palmotea | Hacker News Reader

>> It’s much easier to say someone else’s job is going to be fully replaceable by AI when you don’t actually know what they do.

> Too true. This isn't limited to AI, either.

That's so true there's a term for it: engineer's disease/engineer's syndrome.

https://en.wiktionary.org/wiki/engineer%27s_disease

https://ask.metafilter.com/297591/Origin-of-the-term-Enginee...

View on HN

I wonder if it was (ironically) coined by nonengineers who don't understand how engineers (or other high-stakes professionals at Pareto boundaries) solve problems: by decomposing problems and identifying optional solutions and weighing the solutions based on various risks, trade-offs and tolerances.

I have seen this personally, where merely identifying a possible solution (harmless, reversible) is misinterpreted as selecting and implementing that solution (may be irreversible).

> by decomposing problems and identifying optional solutions and weighing the solutions based on various risks, trade-offs and tolerances.

This is how all people solve problems. Now everyone are not great at all parts, but this really is what anyone does.

Surely the title ”engineer” means something else?

Ideally, but this is not at all taught or incentivized in (American) schools. We're taught to "hack it" which means getting to a solution without much regard for how we got there.

Even if engineers were uniquely capable in this regard it still wouldn't equip them to solve problems in fields where they lack domain expertise.

Again: identifying possible solutions to a problem is not "solving" the problem.

You're right. I'll rephrase: Even if engineers were uniquely capable in this regard it still wouldn't equip them to identify solutions, let alone solve problems, in fields where they lack domain expertise.

I have a bachelor's and masters in engineering and was never taught to "hack it" without regard for how a solution is reached.

Documenting and analyzing your solution is an extremely important part of managing risk, which is what engineers actually do.

Not everyone is going to school for engineering.

I believe it was coined by non-engineers to describe the obnoxious behavior of engineers who arrogantly disrespect other's expertise and assume they're better than non-engineers (when the reality is the engineer doesn't know what he's talking about). Often that involves stupid analogies to things like computer systems.

I mean, if one has a solid physics + engineering background, he is potentially equipped to solve many problems from other fields.

> I mean, if one has a solid physics + engineering background, he is potentially equipped to solve many problems from other fields.

If you've got engineer's disease, those "other fields" include things like psychology and politics. It's a combination of arrogance and myopia.

If your expertise is legitimately relevant and you know where your expertise ends, that's not a problem.

Reply on news.ycombinator.com