<?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/"
		>
<channel>
	<title>Comments on: I Can Outrun a 767</title>
	<atom:link href="http://cafe.elharo.com/programming/i-can-outrun-a-767/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/</link>
	<description>Longer than a blog; shorter than a book</description>
	<lastBuildDate>Wed, 17 Mar 2010 15:48:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: HEEL LIFTS</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-452680</link>
		<dc:creator>HEEL LIFTS</dc:creator>
		<pubDate>Sun, 20 Dec 2009 19:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-452680</guid>
		<description>Excellent work. You have gained a new subscriber. I hope you keep up the good work and I eagerly await more of the absorbing posts.</description>
		<content:encoded><![CDATA[<p>Excellent work. You have gained a new subscriber. I hope you keep up the good work and I eagerly await more of the absorbing posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gewinnspiel</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-200951</link>
		<dc:creator>Gewinnspiel</dc:creator>
		<pubDate>Wed, 05 Mar 2008 23:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-200951</guid>
		<description>OK, so what about the analogy, in other words, what is weather, terrain and surface in the software development world? Perhaps surface could translate to technology, e.g. mud is legacy code, a frozen river is a homogenous environment for which one very suitable technology exists, like Fortran for numeric code, and the outbacks represent a mixed environment? Perhaps the weather could translate to organisational/human aspects, with heavy snow meaning a lot of resistance and little possibility to see far ahead.</description>
		<content:encoded><![CDATA[<p>OK, so what about the analogy, in other words, what is weather, terrain and surface in the software development world? Perhaps surface could translate to technology, e.g. mud is legacy code, a frozen river is a homogenous environment for which one very suitable technology exists, like Fortran for numeric code, and the outbacks represent a mixed environment? Perhaps the weather could translate to organisational/human aspects, with heavy snow meaning a lot of resistance and little possibility to see far ahead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Sands</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-121627</link>
		<dc:creator>David Sands</dc:creator>
		<pubDate>Thu, 23 Aug 2007 12:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-121627</guid>
		<description>I have an interesting anecdote from a late friend of mine. Apparently, during the war they were loading bombs onto a plane. Alas one of them dropped onto the tarmac. Everybody fled the scene post haste. My friend was flat out in a jeep when someone overtook him on a bicycle!
Regards David</description>
		<content:encoded><![CDATA[<p>I have an interesting anecdote from a late friend of mine. Apparently, during the war they were loading bombs onto a plane. Alas one of them dropped onto the tarmac. Everybody fled the scene post haste. My friend was flat out in a jeep when someone overtook him on a bicycle!<br />
Regards David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Smith</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-82163</link>
		<dc:creator>Mike Smith</dc:creator>
		<pubDate>Thu, 26 Apr 2007 21:48:04 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-82163</guid>
		<description>I can believe that of a thoroughbred overbred for short races, but is that true for a more normal working horse like cowboys ride?</description>
		<content:encoded><![CDATA[<p>I can believe that of a thoroughbred overbred for short races, but is that true for a more normal working horse like cowboys ride?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vichy</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-75181</link>
		<dc:creator>Vichy</dc:creator>
		<pubDate>Mon, 09 Apr 2007 09:46:55 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-75181</guid>
		<description>&quot;Itâ€™s like noticing that you walked to the corner store faster than you could drive, and therefore deciding to walk to Tierra del Fuego. Sure you could do it, and you could develop a million-lines-of-code enterprise system without source code control or unit testsâ€“but itâ€™s going to take you hundreds of times longer, and require a lot more pain and effort.&quot;

Excellent!</description>
		<content:encoded><![CDATA[<p>&#8220;Itâ€™s like noticing that you walked to the corner store faster than you could drive, and therefore deciding to walk to Tierra del Fuego. Sure you could do it, and you could develop a million-lines-of-code enterprise system without source code control or unit testsâ€“but itâ€™s going to take you hundreds of times longer, and require a lot more pain and effort.&#8221;</p>
<p>Excellent!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nikolas</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-52322</link>
		<dc:creator>Nikolas</dc:creator>
		<pubDate>Tue, 30 Jan 2007 14:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-52322</guid>
		<description>Sweet :)</description>
		<content:encoded><![CDATA[<p>Sweet <img src='http://cafe.elharo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joachim Zobel</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-33368</link>
		<dc:creator>Joachim Zobel</dc:creator>
		<pubDate>Mon, 27 Nov 2006 22:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-33368</guid>
		<description>Actually the distribution of projects by size is in my experience very far away from being linear. The vast majority of projects are small. The Microsoft empire is built on this.

I disagree that the usefulness of source control is related to project size. It is more related to project duration (that bug has been in for half a year and nobody noticed).</description>
		<content:encoded><![CDATA[<p>Actually the distribution of projects by size is in my experience very far away from being linear. The vast majority of projects are small. The Microsoft empire is built on this.</p>
<p>I disagree that the usefulness of source control is related to project size. It is more related to project duration (that bug has been in for half a year and nobody noticed).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-28340</link>
		<dc:creator>Jonas</dc:creator>
		<pubDate>Wed, 08 Nov 2006 11:33:57 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-28340</guid>
		<description>As soon as unit testing enters a project there&#039;s (or at least should be) two independent implementations of each interface ...</description>
		<content:encoded><![CDATA[<p>As soon as unit testing enters a project there&#8217;s (or at least should be) two independent implementations of each interface &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hallvard TrÃ¦tteberg</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-26857</link>
		<dc:creator>Hallvard TrÃ¦tteberg</dc:creator>
		<pubDate>Fri, 03 Nov 2006 08:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-26857</guid>
		<description>I liked the analogy, too. E.g., I usually take my bike to work, it takes 4 minutes down and 6 up, while it takes at least 10 to drive and 17 to walk. However, there&#039;s more to a travel than distance. A couple of days ago, we experienced the season&#039;s first snow, and before I have changed the tyres (on both bike and car) it&#039;s better to walk. When there&#039;s a lot of snow and I have to wear a thick jacket, going uphill home is too exhausting, so I prefer walking. On longer travels in the terrain, skis are fastest (and often the only possibility). The fastest way of travelling by &quot;foot&quot; is using skates, but of course that requires a frozen and smooth river.

OK, so what about the analogy, in other words, what is weather, terrain and surface in the software development world? Perhaps surface could translate to technology, e.g. mud is legacy code, a frozen river is a homogenous environment for which one very suitable technology exists, like Fortran for numeric code, and the outbacks represent a mixed environment? Perhaps the weather could translate to organisational/human aspects, with heavy snow meaning a lot of resistance and little possibility to see far ahead.

The point isn&#039;t to make a perfect fit, but to see that distance isn&#039;t the only important characteristic of a travel. The distance aspect leads to heuristics like &quot;if you don&#039;t know how long the journey will be, you should prepare for a longer one than what you expect&quot;. However, including weather, surface and terrain in the analogy leads to a richer set of problems. If it&#039;s realistic that it will both be rainy, snowy, windy, freezy etc. in the same project, how should you plan? E.g. we always pack extra food and bring a showel on trips in the snowy, Norwegian mountains, because a heavy snowfall could prevent us from going straight home. How far you can see from the start, how well you know the conditions (I&#039;ve seen women wearing high-healed shoes in the Grand Canyon), how much change you may expect during the travel, may be just as important as the travel distance.</description>
		<content:encoded><![CDATA[<p>I liked the analogy, too. E.g., I usually take my bike to work, it takes 4 minutes down and 6 up, while it takes at least 10 to drive and 17 to walk. However, there&#8217;s more to a travel than distance. A couple of days ago, we experienced the season&#8217;s first snow, and before I have changed the tyres (on both bike and car) it&#8217;s better to walk. When there&#8217;s a lot of snow and I have to wear a thick jacket, going uphill home is too exhausting, so I prefer walking. On longer travels in the terrain, skis are fastest (and often the only possibility). The fastest way of travelling by &#8220;foot&#8221; is using skates, but of course that requires a frozen and smooth river.</p>
<p>OK, so what about the analogy, in other words, what is weather, terrain and surface in the software development world? Perhaps surface could translate to technology, e.g. mud is legacy code, a frozen river is a homogenous environment for which one very suitable technology exists, like Fortran for numeric code, and the outbacks represent a mixed environment? Perhaps the weather could translate to organisational/human aspects, with heavy snow meaning a lot of resistance and little possibility to see far ahead.</p>
<p>The point isn&#8217;t to make a perfect fit, but to see that distance isn&#8217;t the only important characteristic of a travel. The distance aspect leads to heuristics like &#8220;if you don&#8217;t know how long the journey will be, you should prepare for a longer one than what you expect&#8221;. However, including weather, surface and terrain in the analogy leads to a richer set of problems. If it&#8217;s realistic that it will both be rainy, snowy, windy, freezy etc. in the same project, how should you plan? E.g. we always pack extra food and bring a showel on trips in the snowy, Norwegian mountains, because a heavy snowfall could prevent us from going straight home. How far you can see from the start, how well you know the conditions (I&#8217;ve seen women wearing high-healed shoes in the Grand Canyon), how much change you may expect during the travel, may be just as important as the travel distance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry</title>
		<link>http://cafe.elharo.com/programming/i-can-outrun-a-767/comment-page-1/#comment-26747</link>
		<dc:creator>Barry</dc:creator>
		<pubDate>Thu, 02 Nov 2006 19:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/programming/i-can-outrun-a-767/#comment-26747</guid>
		<description>Learning advanced techniques for large programs while writing small programs makes sense in school as long as it is pointed out that the student is learning a technique and that it will not make sense to apply it in the workplace for small programs.  School IS where you are introduced to advanced techniques, though the need to cover many of them in a short time doesn&#039;t allow their application where they would be the most useful.</description>
		<content:encoded><![CDATA[<p>Learning advanced techniques for large programs while writing small programs makes sense in school as long as it is pointed out that the student is learning a technique and that it will not make sense to apply it in the workplace for small programs.  School IS where you are introduced to advanced techniques, though the need to cover many of them in a short time doesn&#8217;t allow their application where they would be the most useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
