BT and tables or software. Gue is about planning and backup planning. When you plan a dive to say 50 meters or 150 ft for 40 minutes, there is a way to adjust deco if the actual average depth is more (or less) than planned. Or if you overstay your time at depth.
It is not about the way you plan your dive (of course there are different ways!) but about the fact that if you have planned your dive, why would you need a computer with you underwater?
But lets agree to disagree because it seems we are
I wish you plenty of good dives with or without computer
It is not really a matter of not liking computers. It's more a question of needing (or that lack of that) one. As said, we plan our dives and have a method of adjusting that plan if the average depth or the bottom time changes.
Having this method eliminates problems like differing algorithms producing different outcomes. That may not sound like a big deal but at depths of 60 m or 180 feet plus a minute more bottom time makes for a lot more deco. Having a set plan and a bottom timer eliminates discrepancies and misunderstandings during the dive.
For 30 m or 100 ft dives that is not a big deal. But Gue trains with the end in mind so even at rec levels you are trained as if your end goal is tech 2 or cave 2.
It just makes no sense to train students in using computers and then telling them they don't need them when they progress to tech 1 or cave 1.
I was thoroughly trained in and even required to use the methods being described for several years. Everyone in our dive group used these methods. The thinking was that a computer can make a mistake, so it is better to use "the computer between your ears." I did all of this using a simple Uwatec bottom timer. In my experience, though, if you choose to go this route, there is an advantage to using a computer in gauge mode instead. Here is an example of why this is true.
Two friends of mine were doing a decompression dive to only 150 feet using their computers in gauge mode and ratio deco to guide their ascents. As trained, they planned the dive carefully, including maximum depth and the ascent profile, and they did their best to follow that plan. Both were certified at the Tech 2 level, so they had lots of experience doing this. They estimated their maximum depths, began their ascents on time, and followed their plan. They were not dummies--one was just completing his Ph.D in software design. The simple math required for this was well within their skill sets.
So why was it an advantage that they were using computers in gauge mode?
After they both got DCS, they were able to download the actual dive profile to see what mistakes they made. It turns out they had dipped below their planned maximum depth enough times in the dive that their average depth for that portion of the dive was about 8 feet deeper than they thought. When they ascended to their first decompression stop, an ascent that should have taken about 30 seconds actually took nearly 3 minutes, and they had not realized that. This means they should have added about two minutes to their bottom time. Finally, they saw that they had miscounted their stop times, shaving 3 minutes off an ascent plan that they actually should have extended by more than a few minutes.
So, because they were using the computers in gauge mode and could check out the details of the dive in the dive log, we all were able to see what mistakes the computers between their ears had made. In all the other cases in which people in our group got DCS while using these dive planning methods, the divers were using simple bottom times and we thus had no way of doing such an analysis.