<?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: Start with something simple</title>
	<atom:link href="http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/feed/" rel="self" type="application/rss+xml" />
	<link>http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/</link>
	<description>Essays on the Continuous Delivery of High Quality Information Systems</description>
	<lastBuildDate>Mon, 22 Feb 2010 09:08:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Corey Ladas</title>
		<link>http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/comment-page-1/#comment-2417</link>
		<dc:creator>Corey Ladas</dc:creator>
		<pubDate>Mon, 12 May 2008 17:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/#comment-2417</guid>
		<description>Perhaps you misunderstand my point.  Dijkstra&#039;s opinion about unit testing is not really relevant to the history of the development of the idea of correctness by construction.  He might not have cared for some of the directions that the idea took, but that does not change the facts of history.

If you read the paragraph that you quoted a little more carefully, I am suggesting that people who are unit testing today can move in the direction of greater rigor if they understand the origin of the practice of test-driven development.  Do you think that Dijkstra would have approved of a suggestion that people should be more formal in their approach?  What would you suggest to the contemporary TDD user?

</description>
		<content:encoded><![CDATA[<p>Perhaps you misunderstand my point.  Dijkstra&#8217;s opinion about unit testing is not really relevant to the history of the development of the idea of correctness by construction.  He might not have cared for some of the directions that the idea took, but that does not change the facts of history.</p>
<p>If you read the paragraph that you quoted a little more carefully, I am suggesting that people who are unit testing today can move in the direction of greater rigor if they understand the origin of the practice of test-driven development.  Do you think that Dijkstra would have approved of a suggestion that people should be more formal in their approach?  What would you suggest to the contemporary TDD user?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: L505</title>
		<link>http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/comment-page-1/#comment-2406</link>
		<dc:creator>L505</dc:creator>
		<pubDate>Fri, 09 May 2008 21:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/#comment-2406</guid>
		<description>&quot;If you are feeling scholarly, Edsger W. Dijkstra’s 1976 book, A Discipline of Programming, explains a design process which is very clearly the origin of both TDD and Design by Contract.  I like to think of TDD as Design by Contract for Dummies, and DbC as Formal Specification for Dummies, so if you’re looking for an opportunity to upgrade your practice, implementing Design by Contract would be an excellent start. And remember, the way to do DbC right is write your postconditions first!&quot;

You ought to do some research and you are taking Dijkstra very out of context - because Dijkstra was violently against &quot;unit testing&quot; and &quot;testing programs&quot;.</description>
		<content:encoded><![CDATA[<p>&#8220;If you are feeling scholarly, Edsger W. Dijkstra’s 1976 book, A Discipline of Programming, explains a design process which is very clearly the origin of both TDD and Design by Contract.  I like to think of TDD as Design by Contract for Dummies, and DbC as Formal Specification for Dummies, so if you’re looking for an opportunity to upgrade your practice, implementing Design by Contract would be an excellent start. And remember, the way to do DbC right is write your postconditions first!&#8221;</p>
<p>You ought to do some research and you are taking Dijkstra very out of context &#8211; because Dijkstra was violently against &#8220;unit testing&#8221; and &#8220;testing programs&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lean Software Engineering</title>
		<link>http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/comment-page-1/#comment-19</link>
		<dc:creator>Lean Software Engineering</dc:creator>
		<pubDate>Mon, 30 Apr 2007 15:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/#comment-19</guid>
		<description>&lt;strong&gt;Avoid dogma when herding cats...&lt;/strong&gt;

So that&#8217;s why XP and TSP are great, but starting with something simple like Scrum can be great advice. That, and avoid dogma when helping your cats to herd themselves.
......</description>
		<content:encoded><![CDATA[<p><strong>Avoid dogma when herding cats&#8230;</strong></p>
<p>So that&#8217;s why XP and TSP are great, but starting with something simple like Scrum can be great advice. That, and avoid dogma when helping your cats to herd themselves.<br />
&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: coreyl</title>
		<link>http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/comment-page-1/#comment-12</link>
		<dc:creator>coreyl</dc:creator>
		<pubDate>Tue, 24 Apr 2007 17:02:13 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/#comment-12</guid>
		<description>Firstly, thank you for the comment.  Let me clarify some terminology.  I am using the words &quot;acceptance test&quot; here in the XP sense i.e. functional verification and validation of a single user story.  So I&#039;m suggesting inserting additional design verification between unit testing and story testing.  Perhaps you had another definition in mind?
</description>
		<content:encoded><![CDATA[<p>Firstly, thank you for the comment.  Let me clarify some terminology.  I am using the words &#8220;acceptance test&#8221; here in the XP sense i.e. functional verification and validation of a single user story.  So I&#8217;m suggesting inserting additional design verification between unit testing and story testing.  Perhaps you had another definition in mind?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/comment-page-1/#comment-11</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 24 Apr 2007 16:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/2007/04/24/start-with-something-simple/#comment-11</guid>
		<description>Putting threat modeling right before acceptance testing is a waste of time.  There&#039;s no time to fix the design problems you&#039;re likely to encounter.</description>
		<content:encoded><![CDATA[<p>Putting threat modeling right before acceptance testing is a waste of time.  There&#8217;s no time to fix the design problems you&#8217;re likely to encounter.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.590 seconds -->
