<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Unit Testing: Rules of Thumb</title>
	<atom:link href="http://blog.fedecarg.com/2008/06/17/unit-testing-rules-of-thumb/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fedecarg.com/2008/06/17/unit-testing-rules-of-thumb/</link>
	<description>Simple is better than complex. Complex is better than complicated. &#124; @fedecarg</description>
	<lastBuildDate>Mon, 06 Feb 2012 14:38:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Luke Samad</title>
		<link>http://blog.fedecarg.com/2008/06/17/unit-testing-rules-of-thumb/#comment-1958</link>
		<dc:creator><![CDATA[Luke Samad]]></dc:creator>
		<pubDate>Tue, 09 Dec 2008 20:54:24 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=233#comment-1958</guid>
		<description><![CDATA[If you are not using &quot;Test-Driven Development&quot; then you will pay in the long run once the code goes into production. Whether it is during enhancements, refactoring, or bug fixes, the costs will add up over time. Sure you can develop without them, but then I hope you don’t hand the junk off to someone else. 

In my experience, maintaining an application without unit tests is extremely difficult and time consuming. It’s completely inefficient unless you wrote the code yourself. 

The reason for &quot;Test-Driven Development&quot; is far more reaching then just the development life cycle. You need to years into the future and tabulate those costs.]]></description>
		<content:encoded><![CDATA[<p>If you are not using &#8220;Test-Driven Development&#8221; then you will pay in the long run once the code goes into production. Whether it is during enhancements, refactoring, or bug fixes, the costs will add up over time. Sure you can develop without them, but then I hope you don’t hand the junk off to someone else. </p>
<p>In my experience, maintaining an application without unit tests is extremely difficult and time consuming. It’s completely inefficient unless you wrote the code yourself. </p>
<p>The reason for &#8220;Test-Driven Development&#8221; is far more reaching then just the development life cycle. You need to years into the future and tabulate those costs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob</title>
		<link>http://blog.fedecarg.com/2008/06/17/unit-testing-rules-of-thumb/#comment-665</link>
		<dc:creator><![CDATA[Jacob]]></dc:creator>
		<pubDate>Mon, 23 Jun 2008 15:36:07 +0000</pubDate>
		<guid isPermaLink="false">http://phpimpact.wordpress.com/?p=233#comment-665</guid>
		<description><![CDATA[Good list. I&#039;m still mulling over the caution about YAGNI. I think its validity might be contingent on the maturity of the individual developer.]]></description>
		<content:encoded><![CDATA[<p>Good list. I&#8217;m still mulling over the caution about YAGNI. I think its validity might be contingent on the maturity of the individual developer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

