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).

▲

fmbb an hour ago | parent [-]

> 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?

▲

pphysch an hour ago | parent [-]

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.

	▲	mrhottakes an hour ago \| parent \| next [-]
		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.
	▲	sporadicism an hour ago \| parent \| prev [-]
		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.