<?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: The Bug is in the Code!</title>
	<atom:link href="http://akfpartners.com/techblog/2008/06/04/the-bug-is-in-the-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://akfpartners.com/techblog/2008/06/04/the-bug-is-in-the-code/</link>
	<description>Technical and Leadership Thoughts</description>
	<pubDate>Tue, 06 Jan 2009 21:20:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cadee</title>
		<link>http://akfpartners.com/techblog/2008/06/04/the-bug-is-in-the-code/comment-page-1/#comment-104</link>
		<dc:creator>Cadee</dc:creator>
		<pubDate>Thu, 23 Oct 2008 06:29:22 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/06/04/the-bug-is-in-the-code/#comment-104</guid>
		<description>Well written article.</description>
		<content:encoded><![CDATA[<p>Well written article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver Schmitz</title>
		<link>http://akfpartners.com/techblog/2008/06/04/the-bug-is-in-the-code/comment-page-1/#comment-103</link>
		<dc:creator>Oliver Schmitz</dc:creator>
		<pubDate>Thu, 19 Jun 2008 16:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://akf-consulting.com/techblog/2008/06/04/the-bug-is-in-the-code/#comment-103</guid>
		<description>Nice article, correlates with my experience.
I would like to add some things:
- Sometimes its not the code but the configuration.
- If the bug is not very obvious, Don't trust nobody when tracing down bugs.
I had to many conversations like :
Me: Are you sure that ?
Op: Yes
Me: Have you checked it?
Op: Yes
Me: Show me!
Op : OOps, I was sure that I checked that.

Another good idea is to have some suitable logging and use these logs. Helps a lot to find the path that fails.

Finally I like the debugging rules found under:
http://www.debuggingrules.com/debuggingrules.jpg

Have fun, Oli</description>
		<content:encoded><![CDATA[<p>Nice article, correlates with my experience.<br />
I would like to add some things:<br />
- Sometimes its not the code but the configuration.<br />
- If the bug is not very obvious, Don&#8217;t trust nobody when tracing down bugs.<br />
I had to many conversations like :<br />
Me: Are you sure that ?<br />
Op: Yes<br />
Me: Have you checked it?<br />
Op: Yes<br />
Me: Show me!<br />
Op : OOps, I was sure that I checked that.</p>
<p>Another good idea is to have some suitable logging and use these logs. Helps a lot to find the path that fails.</p>
<p>Finally I like the debugging rules found under:<br />
<a href="http://www.debuggingrules.com/debuggingrules.jpg" rel="nofollow">http://www.debuggingrules.com/debuggingrules.jpg</a></p>
<p>Have fun, Oli</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.295 seconds -->
