<?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: TDD is the same thing as TFD</title>
	<atom:link href="http://javidjamae.com/2004/07/16/tdd-is-the-same-thing-as-tfd/feed/" rel="self" type="application/rss+xml" />
	<link>http://javidjamae.com/2004/07/16/tdd-is-the-same-thing-as-tfd/</link>
	<description>Javid Jamae's thoughts on Java, software, and other random things</description>
	<pubDate>Thu, 29 Jul 2010 13:12:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Levi</title>
		<link>http://javidjamae.com/2004/07/16/tdd-is-the-same-thing-as-tfd/comment-page-1/#comment-4</link>
		<dc:creator>Levi</dc:creator>
		<pubDate>Thu, 16 Dec 2004 14:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://javidjamae.com/?p=92#comment-4</guid>
		<description>Hey Javid -- I just came across your blog today; Glad to see your speaking up. It's interesting how quickly blogs propogate discussion topics. I posted the following comment on crazybob.org in response to yet another purity argument over whether you're "doing it right". &lt;br /&gt;&lt;br /&gt;Later, &lt;br /&gt;Levi&lt;br /&gt;&lt;br /&gt;----------------------------------------------------&lt;br /&gt;&lt;br /&gt;I'm not convinced it matters one way or the other. More to the point, I don't think test driven and test first are the same thing.&lt;br /&gt;&lt;br /&gt;If you're writing tests and paying attention to what they're telling you, then you're doing TDD.&lt;br /&gt;&lt;br /&gt;Consider how rock climbers make their way up a wall. Sometimes they're pushing, other times they're pulling. Deciding whether it's time to push or pull is a moment to moment decision.&lt;br /&gt;&lt;br /&gt;I say the same applies to testing and coding. Sometimes, you're looking at the code and see exactly what you want to do--so you forge ahead without a test. The key is that you don't go too long. Like the climber you need to notice when you've been pushing too much. Unfortunately, over doing "code-first" doesn't manifest itself as obviously as ultra-tired legs....&lt;br /&gt;&lt;br /&gt;- Levi</description>
		<content:encoded><![CDATA[<p>Hey Javid &#8212; I just came across your blog today; Glad to see your speaking up. It&#8217;s interesting how quickly blogs propogate discussion topics. I posted the following comment on crazybob.org in response to yet another purity argument over whether you&#8217;re &#8220;doing it right&#8221;. </p>
<p>Later, <br />Levi</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>I&#8217;m not convinced it matters one way or the other. More to the point, I don&#8217;t think test driven and test first are the same thing.</p>
<p>If you&#8217;re writing tests and paying attention to what they&#8217;re telling you, then you&#8217;re doing TDD.</p>
<p>Consider how rock climbers make their way up a wall. Sometimes they&#8217;re pushing, other times they&#8217;re pulling. Deciding whether it&#8217;s time to push or pull is a moment to moment decision.</p>
<p>I say the same applies to testing and coding. Sometimes, you&#8217;re looking at the code and see exactly what you want to do&#8211;so you forge ahead without a test. The key is that you don&#8217;t go too long. Like the climber you need to notice when you&#8217;ve been pushing too much. Unfortunately, over doing &#8220;code-first&#8221; doesn&#8217;t manifest itself as obviously as ultra-tired legs&#8230;.</p>
<p>- Levi</p>
]]></content:encoded>
	</item>
</channel>
</rss>
