<?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: No Best Practices</title>
	<atom:link href="http://bassistance.de/2009/04/04/no-best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://bassistance.de/2009/04/04/no-best-practices/</link>
	<description>Jörn Zaefferer on Bass, Geeks and Rock'n'Roll</description>
	<lastBuildDate>Tue, 31 Jan 2012 11:18:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Josh</title>
		<link>http://bassistance.de/2009/04/04/no-best-practices/comment-page-1/#comment-167695</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 09 Jun 2009 20:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://bassistance.de/?p=454#comment-167695</guid>
		<description>But we must have best practices, or the terrorists win.</description>
		<content:encoded><![CDATA[<p>But we must have best practices, or the terrorists win.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jörn</title>
		<link>http://bassistance.de/2009/04/04/no-best-practices/comment-page-1/#comment-163405</link>
		<dc:creator>Jörn</dc:creator>
		<pubDate>Wed, 15 Apr 2009 18:58:38 +0000</pubDate>
		<guid isPermaLink="false">http://bassistance.de/?p=454#comment-163405</guid>
		<description>@tatlar: The sandwich argument illustrates the lack-of-context argument well, nothing more. Touting something as a &quot;best practice&quot; and assuming &quot;software development&quot; as the only context isn&#039;t nearly specific enough. I&#039;m sure there are enough contexts within software development where &quot;test early, test often&quot; isn&#039;t a good advice.</description>
		<content:encoded><![CDATA[<p>@tatlar: The sandwich argument illustrates the lack-of-context argument well, nothing more. Touting something as a &#8220;best practice&#8221; and assuming &#8220;software development&#8221; as the only context isn&#8217;t nearly specific enough. I&#8217;m sure there are enough contexts within software development where &#8220;test early, test often&#8221; isn&#8217;t a good advice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tatlar</title>
		<link>http://bassistance.de/2009/04/04/no-best-practices/comment-page-1/#comment-163404</link>
		<dc:creator>tatlar</dc:creator>
		<pubDate>Wed, 15 Apr 2009 18:38:31 +0000</pubDate>
		<guid isPermaLink="false">http://bassistance.de/?p=454#comment-163404</guid>
		<description>This seems like an argument that boils down to semantics and context. &quot;Test early, test often&quot; is, in the context of the discussion, about software development, not making a sandwich. If you worked in a restaurant kitchen then the &quot;Test early, test often&quot; mantra is not applicable, but the &quot;Wash your hands after going to the bathroom&quot; is.

I agree with what James is saying, but his counter-arguments are assuming that there is no context. He is, after all, a software tester consultant. Does he really think that sandwich makers are reading and commenting on his blog???</description>
		<content:encoded><![CDATA[<p>This seems like an argument that boils down to semantics and context. &#8220;Test early, test often&#8221; is, in the context of the discussion, about software development, not making a sandwich. If you worked in a restaurant kitchen then the &#8220;Test early, test often&#8221; mantra is not applicable, but the &#8220;Wash your hands after going to the bathroom&#8221; is.</p>
<p>I agree with what James is saying, but his counter-arguments are assuming that there is no context. He is, after all, a software tester consultant. Does he really think that sandwich makers are reading and commenting on his blog???</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
