<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: IT Management Lessons from Scuba Diving</title>
	<atom:link href="http://vaughanmerlyn.com/2009/04/30/it-management-lessons-from-scuba-diving/feed/" rel="self" type="application/rss+xml" />
	<link>http://vaughanmerlyn.com/2009/04/30/it-management-lessons-from-scuba-diving/</link>
	<description>Vaughan Merlyn on the Changing Role of the IT Organization</description>
	<lastBuildDate>Tue, 15 May 2012 12:38:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Neil</title>
		<link>http://vaughanmerlyn.com/2009/04/30/it-management-lessons-from-scuba-diving/#comment-1030</link>
		<dc:creator><![CDATA[Neil]]></dc:creator>
		<pubDate>Fri, 11 Dec 2009 01:48:21 +0000</pubDate>
		<guid isPermaLink="false">http://vaughanmerlyn.com/?p=1359#comment-1030</guid>
		<description><![CDATA[There are a couple of big differences as well.

The biggest is probably that teaching diving is a static target.  There are small incremental changes as we learn more about diving physiology and as new technologies come online, but the same training we delivered 20 years ago will still make a safe diver today.

Technology is a moving target.  A technology certification 20 years ago, even 5 years ago, would be pretty worthless.  Technologies come and go, concepts come and go and come back again (centralized, distributed, back to centralized but renamed cloud computing).

Another big difference is the technology and user interfaces.  In Scuba, the technology has a fundamentally limited set of options and parameters.  While a dive computer is a fairly complex machine, the information exchange with the user is very constrained, being not much more than current depth, dive time, maybe the amount of air left, and time remaining at depth.  Compare that to the information on, say, a simple invoice - the processing is simpler but the information exchange with the user is much greater.

Having said all that, I was going to add something more constructive but I have to go and make dinner.  So sorry, terribly sorry, but I must end now.  I was just checking you were still in GA and couldn&#039;t help but add something.

Cheers, Neil.]]></description>
		<content:encoded><![CDATA[<p>There are a couple of big differences as well.</p>
<p>The biggest is probably that teaching diving is a static target.  There are small incremental changes as we learn more about diving physiology and as new technologies come online, but the same training we delivered 20 years ago will still make a safe diver today.</p>
<p>Technology is a moving target.  A technology certification 20 years ago, even 5 years ago, would be pretty worthless.  Technologies come and go, concepts come and go and come back again (centralized, distributed, back to centralized but renamed cloud computing).</p>
<p>Another big difference is the technology and user interfaces.  In Scuba, the technology has a fundamentally limited set of options and parameters.  While a dive computer is a fairly complex machine, the information exchange with the user is very constrained, being not much more than current depth, dive time, maybe the amount of air left, and time remaining at depth.  Compare that to the information on, say, a simple invoice &#8211; the processing is simpler but the information exchange with the user is much greater.</p>
<p>Having said all that, I was going to add something more constructive but I have to go and make dinner.  So sorry, terribly sorry, but I must end now.  I was just checking you were still in GA and couldn&#8217;t help but add something.</p>
<p>Cheers, Neil.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

