Matthew
Contributor
DIR-Atlanta:It's not so much the "use" that is prohibited, as it is the "blind trust in a piece of technology". I often use the following simple analogy to illustrate the difference:
Suppose you are on a cross-country drive in your car, which consistently gets 500 miles from a tank of gas. You see a gas station with a sign out front that says "Next gas station - 100 miles". You notice that you have driven 450 miles since your last fill-up, but your gas gauge still shows a quarter of a tank. Do you blindly trust your gauge, which is telling you that you can make it to the next station with 25 miles to spare, or do you go more by what you know about your own car's gas mileage from driving it?
The "DIR approach" is not to trust the gauge completely, when you have better information available that has been built up through personal experience. The idea is that you should have developed a "feel" for what sorts of profiles you get with tables, before you start using a computer - kind of like learning to add by hand before starting to use a calculator.
A dive computer is just one source of information about decompression profiles, and if you have built up experience with tables beforehand, you will be better equipped to make intelligent decisions about what the computer is telling you (and whether you "believe it" or not).
So using a computer for most rec profiles is generally considered OK, and may in fact be necessary if you are planning to do multiple repetitive dives over the course of several days (and want to get some decent bottom time out of them). Multi-level profiles in particular are pretty hard to manage in any other way.
As several folks have mentioned, once you get into the longer decompression dives, you will want to start relying more on tables for your planning. This gives you the ability to determine a priori how much gas you need, what stops to do, etc. It also allows you to develop and discuss a cohesive dive plan with your team, rather than trying to "wing it" based on what the computer says (or worse, what several of them say).
Well written post, thanks. I think you make a good analogy and your explanation of the DIR approach is easy to understand. And your 5th paragraph describes exactly how we dive, it's somewhat a pleasant surprise reading it in this forum.