News for hackers. Stuff that matters.
Re:The Engineer’s Lament by douche on Monday April 27, 2015 @04:40PM (#9448944)
This seems to be analogous to the Iron Triangle rule: Fast, Cheap or Good, pick two.

You could optimize for perfect engineering, maybe (real-life throws in lots of random, exceptional events, though), but its going to cost you up the wazoo and take forever to finish.

Re:The Engineer’s Lament by antod on Monday April 27, 2015 @08:54PM (#9450022)
Agreed, but with engineering though it's never that binary.

Each dimension is a continuum. You have to end up picking some point on each dimension that is either good enough or the best you can do with your budget also considering that you have to balance this across many many individual decisions. Prioritising these decisions against each other is also done with incomplete information.

As mentioned in the article engineered items are not in a binary state of faulty or not faulty - it's more 'analog' with physical engineering. Rather they have varying degrees of resilience to different often competing failure modes.

And changing requirements can also alter whether something is regarded as adequate or inadequate - eg earthquake strengthening standards for older buildings are a good example.

Engineering isn't about perfection (it can't be), it's about designing solutions that satisfy requirements and specifications as best as possible within constraints while juggling inevitable tradeoffs.