Live data from Hacker News

The Therac-25 Incident (2021)

thedailywtf.com

11–20 of 307 posts

Re: The Therac-25 Incident (2021)

#11
post #3

The most deadly bug in history. If you know any other deadly bug, please share! I love these stories!

The 737 Max MCAS is arguably a bug. That killed 346 people.

Not a "bug" per se, but texting while driving kills ~400 people per year in the US. It's a bug at some level of granularity.

To be tongue in cheek a bit, buggy JIRA latency has probably wasted 10,000 human years. Those are many whole human lives if you count them up.

Re: The Therac-25 Incident (2021)

#13
post #3

The most deadly bug in history. If you know any other deadly bug, please share! I love these stories!

The MCAS related bugs @ Boeing led to 300+ deaths, so it's probably a contender.

Was that a bug or a failure to inform pilots about a new system?

Re: The Therac-25 Incident (2021)

#14
post #3

The most deadly bug in history. If you know any other deadly bug, please share! I love these stories!

Probably many rather than a single bug, but the botched London Ambulance dispatch software from the 90s, is probably one of the most deadly software issues of all time, although there aren't any estimates I know of that try to quantify the number of lives lost as a result.

http://www0.cs.ucl.ac.uk/staff/a.finkelstein/papers/lascase....

Re: The Therac-25 Incident (2021)

#16

> software quality doesn't appear because you have good developers. It's the end result of a process, and that process informs both your software development practices, but also your testing. Your management. Even your sales and servicing. If you only take one thing away from this article, it should be this one! The Therac-25 incident is a horrifying and important part of software history, it's really easy to think t…

This is true but there also needs to be good developers as well. It can't just be great process and low quality developer practices. There needs to be: 1/ high quality individual processes (development being one of them), 2/ high quality delivery mechanisms, 3/ feedback loops to improve that quality, 4/ out of band mechanisms to inspect and improve the quality.

Re: The Therac-25 Incident (2021)

#17
post #13

Earlier quoted context omitted.

The MCAS related bugs @ Boeing led to 300+ deaths, so it's probably a contender.

Was that a bug or a failure to inform pilots about a new system?

Both - and really MCAS was fine but the issue was the metering systems (Pitot tubes) and the handling of conflicting data. That part of the puzzle was definitely a bug in the logic/software.

Re: The Therac-25 Incident (2021)

#19
post #13

Earlier quoted context omitted.

The MCAS related bugs @ Boeing led to 300+ deaths, so it's probably a contender.

Was that a bug or a failure to inform pilots about a new system?

In the same vein one could argue that Therac-25 was not actually a software bug but a hardware problem. Interlocks, that could have prevented the accidents and that where present in earlier Therac models, were missing. The software was written with those interlocks in mind. Greedy management/hardware engineers skipped them for the -25 version.

It's almost never just software. It's almost never just one cause.

Re: The Therac-25 Incident (2021)

#20
post #9

I strongly believe that we will see an incident akin to Therac-25 in the near future. With as many people running YOLO mode on their agents as there are, Claude or Gemini is going to be hooked up to some real hardware that will end up killing someone. Personally, I've found even the latest batch of agents fairly poor at embedded systems, and I shudder at the thought of giving them the keys to the kingdom to say... a…

The 737 MAX MCAS debacle was one such failure, albeit involving a wider system failure and not purely software.

Agreed on the future but I think we were headed there regardless.

Post reply on HN