<?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: Does it make you slower?</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/12/25/tdd-does-it-make-you-slower/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/12/25/tdd-does-it-make-you-slower/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Tue, 16 Mar 2010 05:27:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Vikas Kerni</title>
		<link>http://www.markhneedham.com/blog/2008/12/25/tdd-does-it-make-you-slower/comment-page-1/#comment-2274</link>
		<dc:creator>Vikas Kerni</dc:creator>
		<pubDate>Fri, 26 Dec 2008 02:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=768#comment-2274</guid>
		<description>Excellent Post.
I would like to add more.

My thinking is that whole argument is wrong. TDD means writing a failing test first and then writing your programs. When you estimate every programming task, you also allocate unit testing also. Programmer has the privilege either to automate the unit test or manually test the program. Automated system will save the programmer to manually test the system whenever he makes the change. 
So, a TDD based approach with right programmers should save time. 

5. Basically the real argument is whether building industrial strength applications takes more time than non-industrial application. Answer is yes. TDD means that one has to adopt multi-layer and multi-tiered architecture. If you don&#039;t want enterprise application, TDD is not for you


http://vikasnetdev.blogspot.com/2008/12/does-tdd-mean-less-roi-return-on.html</description>
		<content:encoded><![CDATA[<p>Excellent Post.<br />
I would like to add more.</p>
<p>My thinking is that whole argument is wrong. TDD means writing a failing test first and then writing your programs. When you estimate every programming task, you also allocate unit testing also. Programmer has the privilege either to automate the unit test or manually test the program. Automated system will save the programmer to manually test the system whenever he makes the change.<br />
So, a TDD based approach with right programmers should save time. </p>
<p>5. Basically the real argument is whether building industrial strength applications takes more time than non-industrial application. Answer is yes. TDD means that one has to adopt multi-layer and multi-tiered architecture. If you don't want enterprise application, TDD is not for you</p>
<p><a href="http://vikasnetdev.blogspot.com/2008/12/does-tdd-mean-less-roi-return-on.html" rel="nofollow">http://vikasnetdev.blogspot.com/2008/12/does-tdd-mean-less-roi-return-on.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
