top | item 45529495

(no title)

AzN1337c0d3r | 4 months ago

Not to be pedantic, but people have died from software programming bugs being a primary contributing factor. One example: Therac-25 (https://en.wikipedia.org/wiki/Therac-25)

discuss

order

gkedzierski|4 months ago

I only meant this in relation to Crowdstrike incident that was mentioned in the comment I replied to. The standards and regulations in those other industries have changed dramatically (for the better) since Theract-25.

Leherenn|4 months ago

I mean, that was over 40y ago. Same thing for the Ariane 5 failure which is a staple of safety-critical classes (at least in Europe), it's not getting any younger.

If all the examples you can conjure are decades old*, is it any wonder that people don't really take it seriously? Software power the whole world, and yet the example of critical failure we constantly hear about is close to half a century old?

I think the more insidious thing is all the "minor" pains being inflicted by software bugs, that when summed up reach crazy level of harm. It's just diluted so less striking. But even then, it's hard to say if the alternative of not using software would have been better overall.

* maybe they've added Boeing 737 Max to the list now?

AzN1337c0d3r|4 months ago

> If all the examples you can conjure are decades old

They're not ALL the examples I can conjure up. MCAS would probably be an example of a modern software bug that killed a bunch of people.

How about the 1991 failure of the Patriot missile to defend against a SCUD missile due to a software bug not accounting for clock drift, causing 28 lives lost?

Or the 2009 loss of Air France 447 where the software displayed all sorts of confusing information in what was an unreliable airspeed situation?

Old incidents are the most likely to be widely disseminated, which is why they're most likely to be discussed, but that doesn't mean that the discussion resolving around old events mean the situation isn't happening now.