How history's worst software error weaponized a radiation machine

https://youtube.com/watch?v=Ap0orGCiou8

>deciding how to inform users they could be about to deliver a lethal dose of radiation to their patient

>"MALFUNCTION 54"

>refuses to elaborate

>leaves company

:gigachad#:

Rly tho this is horrifying and a good reminder of why QA and code reviews are important. Imagine trusting your life to a program written solo by some random neurodivergent "code hobbyist."

10
Jump in the discussion.

No email address required.

Rly tho this is horrifying and a good reminder of why QA and code reviews are important.

More people argue, convincingly, that the lesson is "don't rely on a single implementation for a critical safety function." Even if the software was perfect, what if a sensor reports incorrectly, like on the crashed 373 MAX jets?

Jump in the discussion.

No email address required.

For sure, there should have been multiple failsafes, including hardware ones, like the vid mentions. But I'm just a programmer so the absolute r-sluration of the software irks me

Jump in the discussion.

No email address required.

I haven't seen the video, but I'm very familiar with this story (and the removal of hardware safeguards from the troublesome model).

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.