<?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"
	>
<channel>
	<title>Comments on: The Importance of Being Wrong (and in the Right Way)</title>
	<atom:link href="http://cafe.elharo.com/debugging/the-importance-of-being-wrong-and-in-the-right-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/debugging/the-importance-of-being-wrong-and-in-the-right-way/</link>
	<description>Longer than a blog; shorter than a book</description>
	<pubDate>Tue, 06 Jan 2009 22:31:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Gabe</title>
		<link>http://cafe.elharo.com/debugging/the-importance-of-being-wrong-and-in-the-right-way/#comment-17457</link>
		<dc:creator>Gabe</dc:creator>
		<pubDate>Fri, 22 Sep 2006 21:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/debugging/the-importance-of-being-wrong-and-in-the-right-way/#comment-17457</guid>
		<description>Debugging is generally a binary search proposition.  The best programmer is the one who can most neatly divide the potential problem space in half.

For particularly challenging problems, running a number of these tests builds up a collection of forensic information that can be interpretted.  The trick is being able to interpret all those bits of information simultaneously.  I don't know how many times the solution to a bug should have been obvious based on my combined testing, but I wasn't keeping all the evidence organized in my head.</description>
		<content:encoded><![CDATA[<p>Debugging is generally a binary search proposition.  The best programmer is the one who can most neatly divide the potential problem space in half.</p>
<p>For particularly challenging problems, running a number of these tests builds up a collection of forensic information that can be interpretted.  The trick is being able to interpret all those bits of information simultaneously.  I don&#8217;t know how many times the solution to a bug should have been obvious based on my combined testing, but I wasn&#8217;t keeping all the evidence organized in my head.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cowan</title>
		<link>http://cafe.elharo.com/debugging/the-importance-of-being-wrong-and-in-the-right-way/#comment-17373</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Fri, 22 Sep 2006 13:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/debugging/the-importance-of-being-wrong-and-in-the-right-way/#comment-17373</guid>
		<description>"Give me a fruitful error any time, full of seeds, bursting with its own corrections. You can keep your sterile truth to yourself."

(a certain Pareto's reply to Kepler, quoted by Stephen Jay Gould in &lt;i&gt;Hen's Teeth and Horse's Toes&lt;/i&gt;)</description>
		<content:encoded><![CDATA[<p>&#8220;Give me a fruitful error any time, full of seeds, bursting with its own corrections. You can keep your sterile truth to yourself.&#8221;</p>
<p>(a certain Pareto&#8217;s reply to Kepler, quoted by Stephen Jay Gould in <i>Hen&#8217;s Teeth and Horse&#8217;s Toes</i>)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
