<?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 Voodoo Magic School of Software Engineering</title>
	<atom:link href="http://www.conifersystems.com/2008/09/11/voodoo-magic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.conifersystems.com/2008/09/11/voodoo-magic/</link>
	<description></description>
	<pubDate>Tue, 07 Sep 2010 21:54:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Continuous Process Improvement - Conifer Systems</title>
		<link>http://www.conifersystems.com/2008/09/11/voodoo-magic/#comment-72</link>
		<dc:creator>Continuous Process Improvement - Conifer Systems</dc:creator>
		<pubDate>Tue, 25 Nov 2008 21:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.conifersystems.com/?p=37#comment-72</guid>
		<description>[...] for the root cause of each problem and fix the root cause so the problem cannot happen again.  (I&#8217;ve written previously on this topic.)  One simple method Toyota adopted to identify root causes is called the &#8220;5 Whys.&#8221;  [...]</description>
		<content:encoded><![CDATA[<p>[...] for the root cause of each problem and fix the root cause so the problem cannot happen again.  (I&#8217;ve written previously on this topic.)  One simple method Toyota adopted to identify root causes is called the &#8220;5 Whys.&#8221;  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Binary Searching for Bugs - Conifer Systems</title>
		<link>http://www.conifersystems.com/2008/09/11/voodoo-magic/#comment-30</link>
		<dc:creator>Binary Searching for Bugs - Conifer Systems</dc:creator>
		<pubDate>Wed, 15 Oct 2008 16:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.conifersystems.com/?p=37#comment-30</guid>
		<description>[...] Normally, when debugging, I would recommend starting from first principles and trying to understand the problem&#8217;s root cause before doing anything else.  Without a complete understanding of the bug, your chances of implementing a complete and correct fix are poor.  The last thing you want to do is apply a random fix that &#8220;seems to work&#8221; without understanding why it works; at that point, you&#8217;re a member of the Voodoo Magic School of Software Engineering. [...]</description>
		<content:encoded><![CDATA[<p>[...] Normally, when debugging, I would recommend starting from first principles and trying to understand the problem&#8217;s root cause before doing anything else.  Without a complete understanding of the bug, your chances of implementing a complete and correct fix are poor.  The last thing you want to do is apply a random fix that &#8220;seems to work&#8221; without understanding why it works; at that point, you&#8217;re a member of the Voodoo Magic School of Software Engineering. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
