<?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: &#8220;Good enough,&#8221; reconsidered</title>
	<atom:link href="http://www.yourdonreport.com/index.php/2006/06/02/good-enough-reconsidered/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yourdonreport.com/index.php/2006/06/02/good-enough-reconsidered/</link>
	<description>Blogging the impact of computer-related technology trends, and whatever else catches my interest.</description>
	<lastBuildDate>Wed, 04 Jan 2012 20:22:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bad Enough - The Yourdon Report - Blogging the impact of computer-related technology trends, and whatever else catches my interest.</title>
		<link>http://www.yourdonreport.com/index.php/2006/06/02/good-enough-reconsidered/comment-page-1/#comment-27385</link>
		<dc:creator>Bad Enough - The Yourdon Report - Blogging the impact of computer-related technology trends, and whatever else catches my interest.</dc:creator>
		<pubDate>Sat, 12 Jan 2008 01:59:29 +0000</pubDate>
		<guid isPermaLink="false">http://yourdon.com/personal/blog/?p=89#comment-27385</guid>
		<description>[...] (see, for example, this recent post about the &#8220;good enough&#8221; nature of Twitter, and this somewhat older one of a more general nature), but it occurred to me that I should acknowledge the opposite end of the [...]</description>
		<content:encoded><![CDATA[<p>[...] (see, for example, this recent post about the &#8220;good enough&#8221; nature of Twitter, and this somewhat older one of a more general nature), but it occurred to me that I should acknowledge the opposite end of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Yourdon Report &#187; Blog Archive &#187; What can software engineers learn from the Facebook flap?</title>
		<link>http://www.yourdonreport.com/index.php/2006/06/02/good-enough-reconsidered/comment-page-1/#comment-1531</link>
		<dc:creator>The Yourdon Report &#187; Blog Archive &#187; What can software engineers learn from the Facebook flap?</dc:creator>
		<pubDate>Sun, 10 Sep 2006 13:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://yourdon.com/personal/blog/?p=89#comment-1531</guid>
		<description>[...] The second most impressive thing Zuckerberg and his colleagues did was to fix the mistake, muy pronto. Of course, they could have retreated completely by removing the code, and reverting to the previous version of their software; but instead, it appears that they introduced some user-controllable options that should have been there in the first place &#8212; i.e., options that allow each Facebook customer to control which of his personal attributes (likes, dislikes, single/&#8221;involved&#8221; relationship status, etc.) can be shared, and which ones cannot. I don&#8217;t know how much code was involved, and I don&#8217;t know how well it was written, and I don&#8217;t know how well they tested it - but getting all of that specified, designed, coded, tested, and deployed in two days is pretty good. Well, in any case, it&#8217;s probably &#8220;good enough,&#8221; from the perspective of the 700,000 grumpy users who thought the whole thing was a bad idea. [...]</description>
		<content:encoded><![CDATA[<p>[...] The second most impressive thing Zuckerberg and his colleagues did was to fix the mistake, muy pronto. Of course, they could have retreated completely by removing the code, and reverting to the previous version of their software; but instead, it appears that they introduced some user-controllable options that should have been there in the first place &#8212; i.e., options that allow each Facebook customer to control which of his personal attributes (likes, dislikes, single/&#8221;involved&#8221; relationship status, etc.) can be shared, and which ones cannot. I don&#8217;t know how much code was involved, and I don&#8217;t know how well it was written, and I don&#8217;t know how well they tested it &#8211; but getting all of that specified, designed, coded, tested, and deployed in two days is pretty good. Well, in any case, it&#8217;s probably &#8220;good enough,&#8221; from the perspective of the 700,000 grumpy users who thought the whole thing was a bad idea. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Yourdon Report &#187; Blog Archive &#187; Ed Foster on the Source of Bad Software</title>
		<link>http://www.yourdonreport.com/index.php/2006/06/02/good-enough-reconsidered/comment-page-1/#comment-786</link>
		<dc:creator>The Yourdon Report &#187; Blog Archive &#187; Ed Foster on the Source of Bad Software</dc:creator>
		<pubDate>Wed, 16 Aug 2006 02:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://yourdon.com/personal/blog/?p=89#comment-786</guid>
		<description>[...] If you haven&#8217;t heard of this concept before, you may well have a strong negative reaction to it. I first started writing about good-enough software about 10 years ago, and I posted a blog entry about it a couple months ago; you can even find a Wikipedia article on the &#8220;principle of good enough.&#8221; Bottom line: mediocre software survives because society tolerates it, and believes (rightly or wrongly) that it really is good enough. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you haven&#8217;t heard of this concept before, you may well have a strong negative reaction to it. I first started writing about good-enough software about 10 years ago, and I posted a blog entry about it a couple months ago; you can even find a Wikipedia article on the &#8220;principle of good enough.&#8221; Bottom line: mediocre software survives because society tolerates it, and believes (rightly or wrongly) that it really is good enough. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

