<?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 &#8211; Test Driven Dogma</title>
	<atom:link href="http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/feed/" rel="self" type="application/rss+xml" />
	<link>http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=tdd-test-driven-dogma</link>
	<description></description>
	<lastBuildDate>Tue, 07 Feb 2012 23:42:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Dedra Fields</title>
		<link>http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/comment-page-1/#comment-37084</link>
		<dc:creator>Dedra Fields</dc:creator>
		<pubDate>Thu, 13 Nov 2008 03:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/#comment-37084</guid>
		<description>3mx9drf94vasrbrg</description>
		<content:encoded><![CDATA[<p>3mx9drf94vasrbrg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: trasa</title>
		<link>http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/comment-page-1/#comment-32840</link>
		<dc:creator>trasa</dc:creator>
		<pubDate>Wed, 17 Sep 2008 16:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/#comment-32840</guid>
		<description>@chris: &quot;what is the cost of NOT doing something.&quot;

Exactly my point.  Always consider your approach.</description>
		<content:encoded><![CDATA[<p>@chris: &#8220;what is the cost of NOT doing something.&#8221;</p>
<p>Exactly my point.  Always consider your approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Brandsma</title>
		<link>http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/comment-page-1/#comment-32833</link>
		<dc:creator>Chris Brandsma</dc:creator>
		<pubDate>Wed, 17 Sep 2008 16:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/#comment-32833</guid>
		<description>I would add the the equation: what is the cost of NOT doing something.

(I&#039;m assuming some of this is coming from my interfaces post: http://elegantcode.com/2008/09/11/are-net-interfaces-required/)

The smaller the project, and the less complex, the less you see a benefit from various techniques. 

I was reading Domain Driven Design (DDD) by Eric Evans a while back.  He does NOT recommend you use DDD for every project.  For some applications, a smart client approach (direct databinding to a form) will provide the same results much faster.  But on larger, more complex applications, a DDD approach is very valid.  I&#039;ve even seen these two approaches used in the same application from time to time.

But where EVERYONE has issues is what do do when applications grow.  Not all applications do this, but enough do to cause issues.  If you created the project using a smart client approach, you can end up with a lot more work to incorporate new features.  If you take the full TDD approach, you might have done a lot of work for nothing.

Trade-offs continue.</description>
		<content:encoded><![CDATA[<p>I would add the the equation: what is the cost of NOT doing something.</p>
<p>(I&#8217;m assuming some of this is coming from my interfaces post: <a href="http://elegantcode.com/2008/09/11/are-net-interfaces-required/)" rel="nofollow">http://elegantcode.com/2008/09/11/are-net-interfaces-required/)</a></p>
<p>The smaller the project, and the less complex, the less you see a benefit from various techniques. </p>
<p>I was reading Domain Driven Design (DDD) by Eric Evans a while back.  He does NOT recommend you use DDD for every project.  For some applications, a smart client approach (direct databinding to a form) will provide the same results much faster.  But on larger, more complex applications, a DDD approach is very valid.  I&#8217;ve even seen these two approaches used in the same application from time to time.</p>
<p>But where EVERYONE has issues is what do do when applications grow.  Not all applications do this, but enough do to cause issues.  If you created the project using a smart client approach, you can end up with a lot more work to incorporate new features.  If you take the full TDD approach, you might have done a lot of work for nothing.</p>
<p>Trade-offs continue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Battaile Fauber</title>
		<link>http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/comment-page-1/#comment-32810</link>
		<dc:creator>Battaile Fauber</dc:creator>
		<pubDate>Wed, 17 Sep 2008 12:49:27 +0000</pubDate>
		<guid isPermaLink="false">http://elegantcode.com/2008/09/16/tdd-test-driven-dogma/#comment-32810</guid>
		<description>Here, here.</description>
		<content:encoded><![CDATA[<p>Here, here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

