I'm not sure I buy that. Or, well, I suppose that those in the medical field believe it, but I don't think they're right.
Consider something like a surgeon nicking and artery while performing some routine surgery, the patient not responding normally to anesthesia or the anesthetist not getting the mixture right and the patient not coming back the way they went in. Or that subset of patients that have poor responses to a vaccine.
Everybody likes to think of the world as a linear system, but it's not.
Well, an equivalent example is really something more like: the surgeon picking up their scalpel too quickly actually means that what they picked up wasn't a scalpel 10% of the time, even though what they saw with their eyes was a scalpel. That's a rather more terrifying error. It's not really possible in the normal world, but is easily possible in the software one (UI not corresponding to the real program state.)
In other words: tangible objects usually correspond to what we see; in software, you have no way necessarily of knowing if the UI/interface is outright lying to you. It could be doing anything internally, and a single flipped bit deep in some subroutine could cause death.
Consider something like a surgeon nicking and artery while performing some routine surgery, the patient not responding normally to anesthesia or the anesthetist not getting the mixture right and the patient not coming back the way they went in. Or that subset of patients that have poor responses to a vaccine.
Everybody likes to think of the world as a linear system, but it's not.