<?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: That sounds unnecessarily uncomfortable</title>
	<atom:link href="http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/</link>
	<description>A weblog about software engineering, Architecture, Technology an other things we like.</description>
	<lastBuildDate>Sat, 28 Jan 2012 20:11:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Not Another TDD Fight! &#8211; Jamie Dobson</title>
		<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/comment-page-1/#comment-24955</link>
		<dc:creator>Not Another TDD Fight! &#8211; Jamie Dobson</dc:creator>
		<pubDate>Mon, 27 Jul 2009 14:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/#comment-24955</guid>
		<description>[...] Response: www.gridshore.nl   This entry was written by Jamie, posted on September 25, 2008 at 12:21 pm, filed under Blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Response: <a href="http://www.gridshore.nl" rel="nofollow">http://www.gridshore.nl</a>   This entry was written by Jamie, posted on September 25, 2008 at 12:21 pm, filed under Blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Le Touilleur Express &#187; TDD : avantages et dangers</title>
		<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/comment-page-1/#comment-8608</link>
		<dc:creator>Le Touilleur Express &#187; TDD : avantages et dangers</dc:creator>
		<pubDate>Tue, 07 Oct 2008 21:35:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/#comment-8608</guid>
		<description>[...] voyons un peu si nous pouvons répondre par quelques contre-arguments. Je vous traduis en partie cet article qui répond directement à &#8220;Cram your test driven [...]</description>
		<content:encoded><![CDATA[<p>[...] voyons un peu si nous pouvons répondre par quelques contre-arguments. Je vous traduis en partie cet article qui répond directement à &#8220;Cram your test driven [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/comment-page-1/#comment-7878</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Fri, 26 Sep 2008 13:51:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/#comment-7878</guid>
		<description>It may well have been useful to be not so black-and-white, I agree.  I suppose I was thinking that the statment was so outrageous, in the mode of &quot;the world is flat&quot;, that I felt saying &quot;that&#039;s a lie&quot; was appropriate.  I see now, maybe it wasn&#039;t.  It felt like a straw man argument, &quot;TDD makes people wants to pass tests, therefore people will tweak code to pass the test instead of getting it working&quot;.  And I was trying to point out that wasn&#039;t an argument, because all types of people game results.</description>
		<content:encoded><![CDATA[<p>It may well have been useful to be not so black-and-white, I agree.  I suppose I was thinking that the statment was so outrageous, in the mode of &#8220;the world is flat&#8221;, that I felt saying &#8220;that&#8217;s a lie&#8221; was appropriate.  I see now, maybe it wasn&#8217;t.  It felt like a straw man argument, &#8220;TDD makes people wants to pass tests, therefore people will tweak code to pass the test instead of getting it working&#8221;.  And I was trying to point out that wasn&#8217;t an argument, because all types of people game results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Bolton</title>
		<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/comment-page-1/#comment-7874</link>
		<dc:creator>Michael Bolton</dc:creator>
		<pubDate>Fri, 26 Sep 2008 13:04:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/#comment-7874</guid>
		<description>&gt;&gt;“and you’ll often find test-driven developers more willing to tweak their final code to match a flawed test than actually fix the test and change their initial design.”

&gt;That is a lie.

It might be useful to note the difference between &quot;that is a lie&quot; and &quot;that is not my experience&quot;.

The debate is hugely entertaining, in the same kind of way that the Wars of the Roses were.  At some point, though, it might be useful to note that software development and engineering are governed by heuristics--fallible methods for solving problems, making decisions, and accomplishing tasks.  Heuristics are presumed to be fallible, context-dependent, constrained by circumstance, enabled by available resources, used by someone with sufficient skill and judgment to make reasonable choices, and conducive to learning.  TDD is a heuristic approach to software development:  often helps; might fail.

---Michael B.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;“and you’ll often find test-driven developers more willing to tweak their final code to match a flawed test than actually fix the test and change their initial design.”</p>
<p>&gt;That is a lie.</p>
<p>It might be useful to note the difference between &#8220;that is a lie&#8221; and &#8220;that is not my experience&#8221;.</p>
<p>The debate is hugely entertaining, in the same kind of way that the Wars of the Roses were.  At some point, though, it might be useful to note that software development and engineering are governed by heuristics&#8211;fallible methods for solving problems, making decisions, and accomplishing tasks.  Heuristics are presumed to be fallible, context-dependent, constrained by circumstance, enabled by available resources, used by someone with sufficient skill and judgment to make reasonable choices, and conducive to learning.  TDD is a heuristic approach to software development:  often helps; might fail.</p>
<p>&#8212;Michael B.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamie</title>
		<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/comment-page-1/#comment-7760</link>
		<dc:creator>Jamie</dc:creator>
		<pubDate>Thu, 25 Sep 2008 11:34:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/#comment-7760</guid>
		<description>Well,

It&#039;s one of them isn&#039;t it?  A storm in a teacup?  Sam, the author of the other article (and I have tried to log in to tell him but his site is broken) is, I think, a bit mixed up.  Here is an example: “and you&#039;ll often find test-driven developers more willing to tweak their final code to match a flawed test than actually fix the test and change their initial design.”

That is a lie.  I have seen many people, testers, managers and developers, drop tests, ignore them, comment them out and ignore much more evidence just to push a project through a gate on a spreadsheet.  This is a problem with human nature, not test-driven-developers.  I know, because I use test-driven development and I have never changed code to make a flawed test work. 

I won’t come back on every point, I value my time too much.  But, I will say this, in regards to the religious nature of Agile and TDD, he is right (it’s a shame that he then does what all religious zealots do.  That’s to say, he set up an artificial, black-and-white argument, putting himself on one side and his, for want of a better word, enemies on the other.  His comparison to Dawkins is powerful.  As an evolutionary biologist Dawkins should be focussing on why we keep reinventing religion and asking  what, if any, is the evolutionary pay back of religion?  Sam, like Dawkins, is focussing on the wrong thing.  Dawkins makes my life as an atheist hard because now the whole world hates us and won’t listen.  His rhetoric is too strong). 

The Americans are somewhat more zealous then we are over here in Europe.  I am thinking of people like Bob Martin and Ron Jeffries.  Martin’s writing I like, Jeffries I don’t.  They sell TDD quite hard, and I think in a very evangelistic manner.  The foot soldiers then pick this up, drive the whole world mad with their self-righteous rhetoric, and drive people like poor Sam mad.  He, in an instant of rage (and good for him for having the courage to question what he sees as dogma), becomes what he beholds  - uninformed and ignorant about this matter.  However, if his central thesis is that TDD needs less rhetoric and less religious overtones, I agree (but, of course agree with hardly anything else in his rant).  I am well in with the agile lot and even I turn green when I hear bullshit spouting from un-informed religious warriors.  Moral of the story, we are all engineers, let’s stick to engineering.  Making stuff, breaking stuff, understanding our tools, writing rants that make people write responses and hence increase knowledge...  Well done Sam, and well done Ben (who I mainly agree with).

And, I hope that we can log into Sam’s site and tell him about this feedback and maybe let him respond.

I have posted both sites on my site, so brace yourselves for a discussion.  http://jamiedobson.co.uk/?q=node/65 

Jamie.</description>
		<content:encoded><![CDATA[<p>Well,</p>
<p>It&#8217;s one of them isn&#8217;t it?  A storm in a teacup?  Sam, the author of the other article (and I have tried to log in to tell him but his site is broken) is, I think, a bit mixed up.  Here is an example: “and you&#8217;ll often find test-driven developers more willing to tweak their final code to match a flawed test than actually fix the test and change their initial design.”</p>
<p>That is a lie.  I have seen many people, testers, managers and developers, drop tests, ignore them, comment them out and ignore much more evidence just to push a project through a gate on a spreadsheet.  This is a problem with human nature, not test-driven-developers.  I know, because I use test-driven development and I have never changed code to make a flawed test work. </p>
<p>I won’t come back on every point, I value my time too much.  But, I will say this, in regards to the religious nature of Agile and TDD, he is right (it’s a shame that he then does what all religious zealots do.  That’s to say, he set up an artificial, black-and-white argument, putting himself on one side and his, for want of a better word, enemies on the other.  His comparison to Dawkins is powerful.  As an evolutionary biologist Dawkins should be focussing on why we keep reinventing religion and asking  what, if any, is the evolutionary pay back of religion?  Sam, like Dawkins, is focussing on the wrong thing.  Dawkins makes my life as an atheist hard because now the whole world hates us and won’t listen.  His rhetoric is too strong). </p>
<p>The Americans are somewhat more zealous then we are over here in Europe.  I am thinking of people like Bob Martin and Ron Jeffries.  Martin’s writing I like, Jeffries I don’t.  They sell TDD quite hard, and I think in a very evangelistic manner.  The foot soldiers then pick this up, drive the whole world mad with their self-righteous rhetoric, and drive people like poor Sam mad.  He, in an instant of rage (and good for him for having the courage to question what he sees as dogma), becomes what he beholds  &#8211; uninformed and ignorant about this matter.  However, if his central thesis is that TDD needs less rhetoric and less religious overtones, I agree (but, of course agree with hardly anything else in his rant).  I am well in with the agile lot and even I turn green when I hear bullshit spouting from un-informed religious warriors.  Moral of the story, we are all engineers, let’s stick to engineering.  Making stuff, breaking stuff, understanding our tools, writing rants that make people write responses and hence increase knowledge&#8230;  Well done Sam, and well done Ben (who I mainly agree with).</p>
<p>And, I hope that we can log into Sam’s site and tell him about this feedback and maybe let him respond.</p>
<p>I have posted both sites on my site, so brace yourselves for a discussion.  <a href="http://jamiedobson.co.uk/?q=node/65" rel="nofollow">http://jamiedobson.co.uk/?q=node/65</a> </p>
<p>Jamie.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jettro</title>
		<link>http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/comment-page-1/#comment-7090</link>
		<dc:creator>jettro</dc:creator>
		<pubDate>Wed, 17 Sep 2008 11:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.gridshore.nl/2008/09/16/that-sounds-unnecessarily-uncomfortable/#comment-7090</guid>
		<description>Again a great article Ben. I also am a strong believer of TDD, not that I am applying it to every line of code I write. Good tests give me comfort to see which tests fall down when I change something. Of course I have to trust the tests, but making a change to code without tests, what should I trust than? My own eyes? Tests make sure a developer starts thinking about what his code should actually do, and as a good side effect, he also checks if the code is useable. To me there are a lot of reasons why you should write tests, they have the most effect when done upfront. When done upfront, they can challenge your design without actually writing code and therefore you can improve the design of your code before you have even started.

greetz Jettro</description>
		<content:encoded><![CDATA[<p>Again a great article Ben. I also am a strong believer of TDD, not that I am applying it to every line of code I write. Good tests give me comfort to see which tests fall down when I change something. Of course I have to trust the tests, but making a change to code without tests, what should I trust than? My own eyes? Tests make sure a developer starts thinking about what his code should actually do, and as a good side effect, he also checks if the code is useable. To me there are a lot of reasons why you should write tests, they have the most effect when done upfront. When done upfront, they can challenge your design without actually writing code and therefore you can improve the design of your code before you have even started.</p>
<p>greetz Jettro</p>
]]></content:encoded>
	</item>
</channel>
</rss>

