<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
	<channel>
		<title>gdp's Comments</title>
		<language>en-us</language>
		<link>https://www.intensedebate.com/users/669150</link>
		<description>Comments by tjstankus</description>
<item>
<title>billchapman.net : The (Some) Fallacies of Test First Development</title>
<link>http://billchapman.net/?p=128#IDComment42449948</link>
<description>I actually think regression and verification are secondary purposes of test-driving code, a nice side-effect if you will. The primary purpose is producing more modular, understandable code. It&amp;#039;s actually pretty tough to write a big pile of junk when you&amp;#039;re being vigilant about test-driving. But I agree with you that TDD/BDD often adds unnecessary overhead when you&amp;#039;re writing a prototype or proof-of-concept.  TDD/BDD is a skill that takes work, like any other. It&amp;#039;s not like you start doing it and suddenly it&amp;#039;s all rainbows and puppies. It&amp;#039;s painful and often slower, especially at first. All that said, I&amp;#039;m anti-dogma of any kind. Do what works for you. But know that TDD/BDD is not a magic light switch. It&amp;#039;s gonna take time and work to get into the groove of it and become test-infected. </description>
<pubDate>Sun, 8 Nov 2009 13:43:00 +0000</pubDate>
<guid>http://billchapman.net/?p=128#IDComment42449948</guid>
</item>	</channel>
</rss>