In mathematics, there's a term not often used called Zequals. It is a method of estimation made by simplifying the math. This method of estimation is surprisingly good.
Here's an explanation, if there are any nerds out there. Anyway, most people mock it because it's less accurate, harder to do, and much slower than a calculator. The point of Zequals is to give people a feel for numbers. Proponents of zequals want to teach it to the youth not so they can crunch Pi to the Billionth digit using it, but so that when they're doing rough calculations in their heads for a less-than-critical design point they can get a good reference number. Opponents of it have no real leg to stand on because the proponents know the limits, know the benefits, and still believe that it gives them a better "feel" for numbers. If nothing else, they can use it to make sure they didn't input something wrong into the calculator.
Now, I'm a 23yo Aerospace Engineering student that uses computers 20 hours a day. I use technology in practically every aspect of my life and am a HUGE proponent of people learning to use technology properly. One of my biggest pet peeves is someone that refuses to "get with the times." I have an RDP on me every time I dive. After my fiancee got certified using an eRDPml, I bought her an RDP and taught her how to use it. Why? I don't trust computers. A responsible person shouldn't. If I get to 130ft and it says my NDL is 18 minutes on air, I instinctively know it's wrong. Why? RDP. Another dive buddy would have NO idea if 18 minutes on air was right or wrong. The scariest one to me is what if you input your EANx mix wrong? That's not a flaw in the computer (which pro-DC people seem to LOVE to flaunt, that they don't "really" fail...we do). However, if it's telling you your MOD on EAN32 is 240ft....would you know it was wrong? How about 180ft? I do it by hand, and I've taught my fiancee to do the same.
I'm in a Senior Design class right now that involves us designing, building, and flying a UAV. One of the most competent members on my team put together the most brilliant structural analysis code and tested every piece of it individually AND together, and validated the data against experimental values. He went WELL above and beyond with the most elaborate Finite Element Analysis model I've ever seen (outside of a proprietary, multi-million dollar code). However, the numbers it gave him were wrong. It could've cost us our grades, graduation, and $10k worth of building materials to learn that the hard way. I had an intuition regarding the accuracy of the program. I knew what the structural capabilities were "supposed" to be. He trusted me because he had no previous experience at this scale and we eventually found an error in his code. It was a "\" instead of a "/". It then gave a number VERY close to what I had estimated. Someone who only works on a computer would have no way of knowing what it "should" be. He didn't. How is a diver supposed to "know" what the limits are if he's only ever dove with a DC?
I think RDP's are a necessary part of learning to become a diver, not because it's the most accurate. Not because it'll give you the best dive profile or that it's the least prone to failure, but because it's the easiest to UNDERSTAND properly. I don't mean learning to use it, I mean really UNDERSTANDING it. There's a huge difference. I dive a DC. If I had the money, I'd get my fiancee one as well (actually, I'd give her mine and get myself a Petrel
.
PS- If I had the patience, I'd go back in and fill in all of the appropriate
emoticons where they should be.