<?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: Believe Defect Free Code is Possible</title>
	<atom:link href="http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/</link>
	<description>Practical methods for successful software management.</description>
	<lastBuildDate>Thu, 06 May 2010 02:07:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Francis</title>
		<link>http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/comment-page-1/#comment-116</link>
		<dc:creator>Francis</dc:creator>
		<pubDate>Wed, 12 Dec 2007 04:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/#comment-116</guid>
		<description>Although I don&#039;t believe in totally &quot;bug&quot; free software, I believe high quality software can be reached practically.  I have seen so many quality software produced by good developer with quality in mind.  They simply put effort into explore the potential problems that can dream of and put in place logics to handle it.  It is also a basic norm that the unexpected should be handled graciously.  This lead to the robustness of products, i.e. quality.

However, today&#039;s attitude has changed totally.  Don&#039;t do anything that has not been asked.  If the product has a warranty period of 10 days, don&#039;t make it work for more than 10 days.  It is because the company want customers to buy another one after the warranty period.

Therefore, if you have asked a feature or capability to handle an exception, don&#039;t expect the product can.</description>
		<content:encoded><![CDATA[<p>Although I don&#8217;t believe in totally &#8220;bug&#8221; free software, I believe high quality software can be reached practically.  I have seen so many quality software produced by good developer with quality in mind.  They simply put effort into explore the potential problems that can dream of and put in place logics to handle it.  It is also a basic norm that the unexpected should be handled graciously.  This lead to the robustness of products, i.e. quality.</p>
<p>However, today&#8217;s attitude has changed totally.  Don&#8217;t do anything that has not been asked.  If the product has a warranty period of 10 days, don&#8217;t make it work for more than 10 days.  It is because the company want customers to buy another one after the warranty period.</p>
<p>Therefore, if you have asked a feature or capability to handle an exception, don&#8217;t expect the product can.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Miller</title>
		<link>http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/comment-page-1/#comment-24</link>
		<dc:creator>Bill Miller</dc:creator>
		<pubDate>Wed, 26 Sep 2007 23:06:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/#comment-24</guid>
		<description>We take for granted the high quality in so many of the products we rely upon in our daily lives, but if they had the quality of many of the software products we use every day, we&#039;d never tolerate it. I&#039;ve always wondered why software seemingly gets a free pass.

In the early days of the internet, like most everyone else, I wanted to see Netscape succeed, and I used their software exclusively for web browsing, but it would always crash.  One day I became so terribly frustrated that I started to use Internet Explorer.  It never crashed. From then on, I never went back.   Low quality has a price when there are alternatives.  High quality software is easily a market differentiator and one easy way for companies to secure a competitive edge, but for some reason, most leaders of companies miss it.

Thanks for commenting Lenny.  Lenny was the director of the product that inspired the article &quot;No Pain, No Gain.&quot;  With Lenny managing, there was no doubt that quality was important and he was willing to take the pain for the gain.  If you&#039;re looking to build great, high quality products, Lenny&#039;s one of the top guys for the job.</description>
		<content:encoded><![CDATA[<p>We take for granted the high quality in so many of the products we rely upon in our daily lives, but if they had the quality of many of the software products we use every day, we&#8217;d never tolerate it. I&#8217;ve always wondered why software seemingly gets a free pass.</p>
<p>In the early days of the internet, like most everyone else, I wanted to see Netscape succeed, and I used their software exclusively for web browsing, but it would always crash.  One day I became so terribly frustrated that I started to use Internet Explorer.  It never crashed. From then on, I never went back.   Low quality has a price when there are alternatives.  High quality software is easily a market differentiator and one easy way for companies to secure a competitive edge, but for some reason, most leaders of companies miss it.</p>
<p>Thanks for commenting Lenny.  Lenny was the director of the product that inspired the article &#8220;No Pain, No Gain.&#8221;  With Lenny managing, there was no doubt that quality was important and he was willing to take the pain for the gain.  If you&#8217;re looking to build great, high quality products, Lenny&#8217;s one of the top guys for the job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lenny Kaplan</title>
		<link>http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/comment-page-1/#comment-16</link>
		<dc:creator>Lenny Kaplan</dc:creator>
		<pubDate>Mon, 24 Sep 2007 00:42:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.yuwantitwhen.com/blog/2007/09/16/believe-defect-free-code-is-possible/#comment-16</guid>
		<description>Long, long ago I had to motivate a newly formed team to produce quality software. In those days when an application crashed so did the entire PC, and developers just accepted rebooting their PC as a necessary part of each user&#039;s work day. We were building a financial terminal for Wall Street and loss of the service, even for a few minutes because our application crashed, could mean significant financial loss for the client if the market moved during the outage. The client would then curse at our field technicians and throw out our product in favor of a competitor. A young developer sitting at their desk far from Wall Street could never fully appreciate that. Back then none of us owned a single share of stock. Instead I told them to think of their application as they do their refrigerator. How would they feel if when they got home from work their refrigerator had shut down, their frozen food thawed, and all they had to do to fix it was to push a little button to restart it. They understood that simple analogy and to this day some 20 years later some team members still remember trying to make their code as solid as as their refrigerator. Quality starts and ends with management support.</description>
		<content:encoded><![CDATA[<p>Long, long ago I had to motivate a newly formed team to produce quality software. In those days when an application crashed so did the entire PC, and developers just accepted rebooting their PC as a necessary part of each user&#8217;s work day. We were building a financial terminal for Wall Street and loss of the service, even for a few minutes because our application crashed, could mean significant financial loss for the client if the market moved during the outage. The client would then curse at our field technicians and throw out our product in favor of a competitor. A young developer sitting at their desk far from Wall Street could never fully appreciate that. Back then none of us owned a single share of stock. Instead I told them to think of their application as they do their refrigerator. How would they feel if when they got home from work their refrigerator had shut down, their frozen food thawed, and all they had to do to fix it was to push a little button to restart it. They understood that simple analogy and to this day some 20 years later some team members still remember trying to make their code as solid as as their refrigerator. Quality starts and ends with management support.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
