Theriac + Saddam ship is not the kind of lore I ever expected to need
_stranger_@lemmy.world
on 12 Sep 11:49
nextcollapse
Had to get x rays the other week and this is all I could think of.
clay_pidgin@sh.itjust.works
on 12 Sep 12:15
collapse
This is a very interesting story. The Theriac 25 is an early computer-controlled tumor irradiating machine, and it had some design flaws that led to patients with radiation burns and at least one death.
The company did many things wrong, it’s an almost idealised example of total failure to take software seriously.
Most importantly they decided they didn’t need to test the software on their new machines because they’d already shipped previous machines running the software, so they “knew it worked”. The previous machines had hardware interlocks that made it impossible for the software to cause a massive dosing errors, the new machine was entirely software controlled.
Also they had exactly 1 “very smart” engineer build the software, who obviously wrote it for a hardware-safe machine. To be fair, I’m sure he was very smart, but safety critical and solo projects are not a great combo.
Also they had no mechanisms to ensure failures would be communicated to their engineers for investigation (failures were reported to them and then dropped into a black hole and forgotten about).
Also they didn’t even have any capability to test their machines after failures started popping up, because they knew the code worked perfectly so they didn’t need to waste any time or money on qa capability, massively slowing down their ability to fix things once people started dying
clay_pidgin@sh.itjust.works
on 12 Sep 22:16
collapse
The single engineer wasn’t mentioned on the podcast, episode but the rest of it was. It’s a really instructive story.
threaded - newest
Theriac + Saddam ship is not the kind of lore I ever expected to need
Had to get x rays the other week and this is all I could think of.
This is a very interesting story. The Theriac 25 is an early computer-controlled tumor irradiating machine, and it had some design flaws that led to patients with radiation burns and at least one death.
A good podcast episode about it. pushkin.fm/…/captain-kirk-forgot-to-put-the-machi…
It’s usually taught in university Computer Science studies in the ethics studies.
Great idea. The company said they couldn’t reproduce the error, but the error was caused by an unplanned user behavior.
The company did many things wrong, it’s an almost idealised example of total failure to take software seriously.
Most importantly they decided they didn’t need to test the software on their new machines because they’d already shipped previous machines running the software, so they “knew it worked”. The previous machines had hardware interlocks that made it impossible for the software to cause a massive dosing errors, the new machine was entirely software controlled.
Also they had exactly 1 “very smart” engineer build the software, who obviously wrote it for a hardware-safe machine. To be fair, I’m sure he was very smart, but safety critical and solo projects are not a great combo.
Also they had no mechanisms to ensure failures would be communicated to their engineer
sfor investigation (failures were reported to them and then dropped into a black hole and forgotten about).Also they didn’t even have any capability to test their machines after failures started popping up, because they knew the code worked perfectly so they didn’t need to waste any time or money on qa capability, massively slowing down their ability to fix things once people started dying
The single engineer wasn’t mentioned on the podcast, episode but the rest of it was. It’s a really instructive story.
Really, the whole podcast is this kind of story.