<?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: Is Troubleshooting an Art or Science?</title>
	<atom:link href="http://repeatgeek.com/technical/is-troubleshooting-an-art-or-science/feed/" rel="self" type="application/rss+xml" />
	<link>http://repeatgeek.com/technical/is-troubleshooting-an-art-or-science/</link>
	<description>Helping geeks achieve success</description>
	<lastBuildDate>Thu, 08 Mar 2012 19:19:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<meta name="generator" content="deStyle 0.9.3" />
	<item>
		<title>By: SteveC</title>
		<link>http://repeatgeek.com/technical/is-troubleshooting-an-art-or-science/comment-page-1/#comment-35</link>
		<dc:creator>SteveC</dc:creator>
		<pubDate>Fri, 06 Nov 2009 00:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://repeatgeek.com/?p=200#comment-35</guid>
		<description>Ages ago, when learning the ropes of SunOs system administration, I was told something which has stuck with me, and served me well, many, many times.  It is similar to your item number 3.

It is this:  &quot;When you really get stuck, and something isn&#039;t working that once worked, try to find something similar to it that still works.  Then gradually change the working system, one thing at a time, to be more like the broken system.&quot;  

Or, in short, compare the working system to the broken system.

This is the fundamental idea behind, for example, git-bisect, but the concept is more general, and extends to hardware, auto mechanics, anything.  It&#039;s really a part of science.  That is, in science, people make hypotheses, do experiments to try to corroborate, and to disprove those hypotheses, and peers try to duplicate the experimental results.    Just because the answers to questions aren&#039;t straightforward doesn&#039;t make something art and not science.  The bleeding edge of science consists of pretty much nothing but questions to which the answers are anything but straightforward.</description>
		<content:encoded><![CDATA[<p>Ages ago, when learning the ropes of SunOs system administration, I was told something which has stuck with me, and served me well, many, many times.  It is similar to your item number 3.</p>
<p>It is this:  &#8220;When you really get stuck, and something isn&#8217;t working that once worked, try to find something similar to it that still works.  Then gradually change the working system, one thing at a time, to be more like the broken system.&#8221;  </p>
<p>Or, in short, compare the working system to the broken system.</p>
<p>This is the fundamental idea behind, for example, git-bisect, but the concept is more general, and extends to hardware, auto mechanics, anything.  It&#8217;s really a part of science.  That is, in science, people make hypotheses, do experiments to try to corroborate, and to disprove those hypotheses, and peers try to duplicate the experimental results.    Just because the answers to questions aren&#8217;t straightforward doesn&#8217;t make something art and not science.  The bleeding edge of science consists of pretty much nothing but questions to which the answers are anything but straightforward.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

