<?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: Forget about Hope Driven Development (HDD), the cancer of software development.</title>
	<atom:link href="http://www.makinggoodsoftware.com/2009/05/12/hdd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/</link>
	<description></description>
	<lastBuildDate>Thu, 04 Mar 2010 11:11:07 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Let Fortune Cookies Develop for you</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-4593</link>
		<dc:creator>Let Fortune Cookies Develop for you</dc:creator>
		<pubDate>Mon, 01 Feb 2010 09:59:10 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-4593</guid>
		<description>[...] recently read an article by Alberto Gutierrez where he&#8217;s talking about a thing he calls &#8216;Hope Driven Development&#8217; or HDD. And I [...]</description>
		<content:encoded><![CDATA[<p>[...] recently read an article by Alberto Gutierrez where he&#8217;s talking about a thing he calls &#8216;Hope Driven Development&#8217; or HDD. And I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Giorgio Sironi</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-4526</link>
		<dc:creator>Giorgio Sironi</dc:creator>
		<pubDate>Sat, 30 Jan 2010 12:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-4526</guid>
		<description>I think for internal parameters the validation issues may be substituted by unit testing. You can check that the parameters passed to your constructors are valid, but this is going to clash with simple unit testing, where you are forced to initialize collaborators you do not use.</description>
		<content:encoded><![CDATA[<p>I think for internal parameters the validation issues may be substituted by unit testing. You can check that the parameters passed to your constructors are valid, but this is going to clash with simple unit testing, where you are forced to initialize collaborators you do not use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FizzBuzz &#187; Cleaning out the Bookmarks #5 &#8211; Hope Driven Development</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-1661</link>
		<dc:creator>FizzBuzz &#187; Cleaning out the Bookmarks #5 &#8211; Hope Driven Development</dc:creator>
		<pubDate>Sun, 25 Oct 2009 16:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-1661</guid>
		<description>[...] http://www.makinggoodsoftware.com/2009/05/12/hdd/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.makinggoodsoftware.com/2009/05/12/hdd/" rel="nofollow">http://www.makinggoodsoftware.com/2009/05/12/hdd/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rodrigo Gama</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-1164</link>
		<dc:creator>Rodrigo Gama</dc:creator>
		<pubDate>Fri, 18 Sep 2009 13:02:55 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-1164</guid>
		<description>See, the problem here is that validating bad parameters turns the code into a mess. It&#039;s an awful lot harder to read a method that contains validation for each parameter...

But I agree it&#039;s necessary. That&#039;s why I would go for TDD (for documenting your assumptions) or DbC (That would be my first choice, definitely).</description>
		<content:encoded><![CDATA[<p>See, the problem here is that validating bad parameters turns the code into a mess. It&#8217;s an awful lot harder to read a method that contains validation for each parameter&#8230;</p>
<p>But I agree it&#8217;s necessary. That&#8217;s why I would go for TDD (for documenting your assumptions) or DbC (That would be my first choice, definitely).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonas</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-1161</link>
		<dc:creator>Jonas</dc:creator>
		<pubDate>Fri, 18 Sep 2009 09:14:54 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-1161</guid>
		<description>Ha! You are not enlightened!
Keep the faith and you will eventually see the light of PDD: Prayer Driven Development:

http://blog.jonasbandi.net/2007/10/introducing-add.html

;-)</description>
		<content:encoded><![CDATA[<p>Ha! You are not enlightened!<br />
Keep the faith and you will eventually see the light of PDD: Prayer Driven Development:</p>
<p><a href="http://blog.jonasbandi.net/2007/10/introducing-add.html" rel="nofollow">http://blog.jonasbandi.net/2007/10/introducing-add.html</a></p>
<p> <img src='http://www.makinggoodsoftware.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary Ellen</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-205</link>
		<dc:creator>Mary Ellen</dc:creator>
		<pubDate>Thu, 09 Jul 2009 18:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-205</guid>
		<description>I just realized that HDD is also a lot of what goes on in the fields of international devt, not just software...hmmm</description>
		<content:encoded><![CDATA[<p>I just realized that HDD is also a lot of what goes on in the fields of international devt, not just software&#8230;hmmm</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-65</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Fri, 15 May 2009 19:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-65</guid>
		<description>Validating input isn&#039;t going to cause performance problems.  Horribly written code will.</description>
		<content:encoded><![CDATA[<p>Validating input isn&#8217;t going to cause performance problems.  Horribly written code will.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miska</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-66</link>
		<dc:creator>Miska</dc:creator>
		<pubDate>Fri, 15 May 2009 13:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-66</guid>
		<description>Nice little piece about one aspect of good programming. The topic is important, and although the few typos irritated my editor&#039;s eye, defensive programming needs to get talked about.
I&#039;ve actually made a profession out of preaching good quality habits to programmers and one of the issues is checking incoming variables. In code reviews - or what I call ticking the code - I apply a rule called CHECK-IN, which asks the checker to tick any variable that is just used without any kind of sanity check. We don&#039;t always need a sanity check, we can&#039;t always perform a sanity check, but we should at the least know when we expose our code to such dangers.
For more information, check www.tick-the-code.com</description>
		<content:encoded><![CDATA[<p>Nice little piece about one aspect of good programming. The topic is important, and although the few typos irritated my editor&#8217;s eye, defensive programming needs to get talked about.<br />
I&#8217;ve actually made a profession out of preaching good quality habits to programmers and one of the issues is checking incoming variables. In code reviews &#8211; or what I call ticking the code &#8211; I apply a rule called CHECK-IN, which asks the checker to tick any variable that is just used without any kind of sanity check. We don&#8217;t always need a sanity check, we can&#8217;t always perform a sanity check, but we should at the least know when we expose our code to such dangers.<br />
For more information, check <a href="http://www.tick-the-code.com" rel="nofollow">http://www.tick-the-code.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 5 Tips for creating good code every day, how to become a good software developer &#171; Making Good Software</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-67</link>
		<dc:creator>5 Tips for creating good code every day, how to become a good software developer &#171; Making Good Software</dc:creator>
		<pubDate>Fri, 15 May 2009 10:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-67</guid>
		<description>[...] checked if the implementation is correct with the customer, that&#8217;s a typical behavior from Hope Driven Development and that&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] checked if the implementation is correct with the customer, that&#8217;s a typical behavior from Hope Driven Development and that&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-05-14 &#171; pabloidz</title>
		<link>http://www.makinggoodsoftware.com/2009/05/12/hdd/comment-page-1/#comment-64</link>
		<dc:creator>links for 2009-05-14 &#171; pabloidz</dc:creator>
		<pubDate>Thu, 14 May 2009 12:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://makinggoodsoftware.com/?p=128#comment-64</guid>
		<description>[...] Forget about Hope Driven Development (HDD), the cancer of software development Making Good Software (tags: programming)         TagsCategoriasmiudezas Uncategorized &#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] Forget about Hope Driven Development (HDD), the cancer of software development Making Good Software (tags: programming)         TagsCategoriasmiudezas Uncategorized &nbsp; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
