View Single Post
Old 28th November 2006, 21:30   #72 (permalink)
PaulTG2
RBW Member
 
PaulTG2's Avatar

Current Rebreather/s:
Megalodon
Classic Kiss

Other Rebreather/s:
Sport Kiss
 
Join Date: Mar 2006
Location: Virginia, USA
Posts: 517
PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light PaulTG2 is a glorious beacon of light
Re: Open source, I see problems. Questions.

Hello,

If you produce better idiot proof systems, the world will produce better idiots.

There are alot of excellent analysis, concepts, thoughts, and discussions provoked from this project. That alone make it well worthwhile.

I do believe there may be a slight balance problem between ease of use, idiot proof systems, and the issues inherent in more complex systems. If a system has twice as many modules then it is likely to have twice as many failures. With more complex systems divers will have a far more difficult time determining what has gone wrong... and the chance of them getting the solution wrong increases. They rely more on the system diagonisis which causes an over reliance on the technology and less reliance on understanding it.

Two examples may help:

The first example: Many people assume a two engine aircraft is far safer than a single engine aircraft. What most people fail to notice is that you will have twice as many engine failures as a result. The chance of shutting down the good engine exists because the pilot mis-reads which engine died. The pilot has more options in a twine .... and more opportunities to make a mistakes.

The second example: Many systems have grown so complex it is difficult, if not impossible, for average people (and sometimes experts) to determine what has gone wrong. Microsoft Windows is an excellent example. It generally doesn't pay to actually try to find out what is going wrong... it's easier to just reboot the machine -- or reinstall the software. That's OK on the desktop... probably not OK on the decktop of a ship at 200' below the surface.

How do you balance the complex system against the idiot, against the mistakes, against failure.... hmm... figure that out and you'll be rich.

Here is the big, big, big rub. Training AND proficiency makes all the difference. PERFECT practice makes for PERFECT performance. Practice maintains proficiency which saves lives.

Bottom line truth: Wether a simple non-redundant system or a complex "fail-safe" system, the training and the diver's practices to maintain proficency will determine if they live or die when something goes wrong.

-p
(Offline)
 
Reply With Quote