<?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: Guest Post: Where there&#8217;s people, there&#8217;s problems</title>
	<atom:link href="http://edgehopper.com/guest-post-where-theres-people-theres-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://edgehopper.com/guest-post-where-theres-people-theres-problems/</link>
	<description>Brain Droppings on Innovation, Creativity, and Collaboration</description>
	<lastBuildDate>Thu, 10 May 2012 09:19:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jurgen Appelo</title>
		<link>http://edgehopper.com/guest-post-where-theres-people-theres-problems/comment-page-1/#comment-2645</link>
		<dc:creator>Jurgen Appelo</dc:creator>
		<pubDate>Sun, 08 Mar 2009 11:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/?p=1346#comment-2645</guid>
		<description>@Vasco:

Sorry, but your arguments are flawed.

One example: &quot;blind spots&quot; or &quot;editing blindness&quot; where people are unable to see the errors in their own work because they&#039;ve been working on it for so long.

The only possible solution is to have someone else inspect (or review) the work. This person will find errors 10x faster than the author himself. Which evidently makes the inspection cheaper than trying to deliver with zero defects.

Sure, TDD can alleviate some of that problem. But I don&#039;t see how to unit test my documents, or my book, or my blog posts.</description>
		<content:encoded><![CDATA[<p>@Vasco:</p>
<p>Sorry, but your arguments are flawed.</p>
<p>One example: &#8220;blind spots&#8221; or &#8220;editing blindness&#8221; where people are unable to see the errors in their own work because they&#8217;ve been working on it for so long.</p>
<p>The only possible solution is to have someone else inspect (or review) the work. This person will find errors 10x faster than the author himself. Which evidently makes the inspection cheaper than trying to deliver with zero defects.</p>
<p>Sure, TDD can alleviate some of that problem. But I don&#8217;t see how to unit test my documents, or my book, or my blog posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vasco Duarte</title>
		<link>http://edgehopper.com/guest-post-where-theres-people-theres-problems/comment-page-1/#comment-2636</link>
		<dc:creator>Vasco Duarte</dc:creator>
		<pubDate>Sat, 07 Mar 2009 19:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/?p=1346#comment-2636</guid>
		<description>I think that you are missing a very important point that basically invalidates your argument altogether.

If you could achieve Zero Defects your process would be much faster infinitely cheaper!

Here&#039;s my argument: http://bit.ly/15lkle</description>
		<content:encoded><![CDATA[<p>I think that you are missing a very important point that basically invalidates your argument altogether.</p>
<p>If you could achieve Zero Defects your process would be much faster infinitely cheaper!</p>
<p>Here&#8217;s my argument: <a href="http://bit.ly/15lkle" rel="nofollow">http://bit.ly/15lkle</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen F. Heffner</title>
		<link>http://edgehopper.com/guest-post-where-theres-people-theres-problems/comment-page-1/#comment-2585</link>
		<dc:creator>Stephen F. Heffner</dc:creator>
		<pubDate>Tue, 03 Mar 2009 08:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://edgehopper.com/?p=1346#comment-2585</guid>
		<description>Isn&#039;t peer review a form of inspection?

I believe a significant part of the answer is in automating the inspection process.  As the author of a software engineering automation meta-tool, I&#039;m deeply involved in the automation of every aspect of software engineering, including analysis, re-engineering, and translation to a different language.  What&#039;s needed, IMHO, is a powerful meta-tool, not a bunch of rigid &quot;point solutions&quot;.  A meta-tool allows you to create your own automation tools rapidly and with low effort.

Another advantage of automating software engineering is that it reduces bugs in the first place.  Once you get the automation rules right, the meta-tool won&#039;t introduce bugs.</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t peer review a form of inspection?</p>
<p>I believe a significant part of the answer is in automating the inspection process.  As the author of a software engineering automation meta-tool, I&#8217;m deeply involved in the automation of every aspect of software engineering, including analysis, re-engineering, and translation to a different language.  What&#8217;s needed, IMHO, is a powerful meta-tool, not a bunch of rigid &#8220;point solutions&#8221;.  A meta-tool allows you to create your own automation tools rapidly and with low effort.</p>
<p>Another advantage of automating software engineering is that it reduces bugs in the first place.  Once you get the automation rules right, the meta-tool won&#8217;t introduce bugs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: edgehopper.com @ 2012-05-17 07:32:14 -->
