Fatal exceptions?

[SJWhiteley]

IMO yes. I'd argue that if the code contained a mistake then it's faulty software. If an error is caused by a user miss-using the delivered software (entering incorrect values etc.) then it's user error. You're 100% right, though, that both are ultimately subsets of "human error".

I'm kind of sensitive to this, at the moment. The machine we have is causing all sorts of quality issues because it's not doing what it should. The response from the engineers (a loose term in this case) is that the program is both working correctly and it's a programming fault.

Regardless, they refuse to admit that there's a problem, and thus cannot do anything about it. When pushed, they simply explain this is how it works and needs more investigation.

I think this is a flaw in software engineering, as taught, in that we are able to divest ourselves of a rather serious responsibility, as the general non-technical public at large accept that software just breaks, regardless of application.

I cannot see a structural engineer shrugging 'oh well, something must have gone wrong' when a bridge fails, and it being taken as an acceptable answer.

[homer13j]

The response from the engineers (a loose term in this case) is that the program is both working correctly and it's a programming fault.