Flutterby™! : Pool portion of PADI open water SCUBA

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Pool portion of PADI open water SCUBA

2016-01-17 05:30:07.802878+00 by Dan Lyke 1 comments

Pool portion of PADI open water SCUBA cert complete. But

comments in ascending chronological order (reverse):

#Comment Re: Pool portion of PADI open water SCUBA made: 2016-01-17 16:28:13.38863+00 by: Dan Lyke

I started to write something about... well... lots of things, but erased it, and then lost the "But" on my tablet. Tablets and phones are still media consumption devices... Anyway, a few notes:

  1. There's a bunch of cognitive load that isn't yet automatic. It's easy to have the snorkel in, and dive. Tracking the computer and the pressure gauge and what I'm doing to equalitze and, especially in the tight confines of the pool where we're swilling tight circles, keeping track of my buddy and whether my tank is listing is still tough.
  2. Loved my instructor, but... I'm not keen on PADI's educational material. Seems like there's a lot of fluff and promotional crap in it, and with that strewn across the important material, it's hard to glean the bits. I'd like to see what SSI's materials look like.
  3. I could spend another pool day working on neutral boyancy. Granted there wasn't much to track depth with (oh, look, different pool wall), and there wasn't a lot of depth to work in, but just trying to float at a level and "oh, my fins just hit the bottom, oh, I'm right near the surface, oh, my fins..." was tough.
  4. It's amazing how much the day took out of me. I need to make sure I don't cramp up today.

Short version: If you have the option to do your closed water as a 2 day, spread that SOB out. Open water next weekend.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.