I'm guessing you're not a trained programmer? Or an engineer? Trust me the pain in this conversation is mutual.
We both have the same goal in that we don't want to see anyone die. Only difference is one of us chooses to just blame people instead of entertaining the thought that maybe, just maybe, we can engineer a better system. Maybe we can prevent scenarios like this from happening through improved product engineering while at the same time NOT have your precious oxygen sensors burn up because your unit's a little wet in the trunk of your car. Maybe these two goals aren't mutually exclusive.
I am a programmer with decades of dealing with building complicated systems for users who expect the speed of light to change, time travel and other ‘but surely...’ requirements to be met.
There is a history of rebreathers trying to be clever. The Sentinal tried very hard and failed. The Poseidon tries still, AP have a bunch of features like the CO2 alarm which are more or less successful. If the Liberty fails it will be because it is too complicated and at the nanny end of the spectrum rather than because it is overly simple without obvious features.
The problem here was failure to have O2 and failure to monitor ppo2. How can we engineer that out? We can easily tell if o2 is flowing (they don’t but it would be easy enough if it helped). So now the question is ‘should o2 be flowing?’ When would that be? Normal operation. When is that? Wet? How about the prebreath? Back on the boat? Deep? How about bailed out? Moving about? Back of car, plane hold, walking between the car and the boat? Maybe I take all those inputs and feed them into some neural net which we train by taking data from all the users. Now when it alarms we have really no idea why.
Next we have the human reaction to alarms.
1 - too many alarms, never seen a real one yet, so ignore it/work round it.
2 - no false alarms so rely on the alarm spotting the problem so I don’t need to worry.
Perhaps the user in this case fell into 2.
There is occasional fierce debate about the spectrum of electronic aids in CCR. From a fully manual unit where the user understands that either they add o2 or die, through the JJ where you need to check the HUD and handsets to notice ppO2 FAILURES but which maintain setpoint, finally to machines which scream when they detect an issue.
I have a machine which relies on red lights to tell me the ppo2 is wrong. Some days I think an audible alarm would be good, but if I had such an alarm would I check for myself so often? So now I am being a bit lazy and the electronics fail completely?
Building a fool proof rebreather is not just about code, controls and monitoring. It is about the whole system including the user. The training and user attitudes are key. Planes may be safer than ever before but we still don’t let just anybody fly an airliner with 300 people on board.
Recreational divers have been using them for 20 or 30 years now and the technology has improved enormously. However, even small incremental ‘improvements’ by the biggest manufacturer have a hard time. Look at user reactions to the AP CO2 monitor.
There is also an argument made that if you can’t save everyone whose gas is off or who assembles the loop backwards then rebreathers are just too dangerous and should not exist.
Hopefully nobody buys a rebreather thinking ‘I might leave the gas off or assemble this backwards’. People should have a good think about whether that is a risk for them personally and we ought not to cast aspirations on those that do think that, or find out the hard way.