<?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: 12 Practical Tips for Building Bug-Free Software</title>
	<atom:link href="http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/</link>
	<description>Our products, programming &#38; business.</description>
	<lastBuildDate>Tue, 09 Feb 2010 18:35:10 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: wikiBuddha</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-53671</link>
		<dc:creator>wikiBuddha</dc:creator>
		<pubDate>Tue, 08 Dec 2009 20:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-53671</guid>
		<description>I actually believe that software can be 100% bug free; or at least 99.99%.

And in an attempt to discredit the possibility, Johnson above, provided a list of examples which unfortunately do not exhibit the same nature as software and accordingly does not hold water.

Unlike his examples, software is not subject to degradation (or is capable of not being so) or mechanical failures. This is not to say that a software-driven system will never exhibit &quot;problems&quot; but that the software has the propensity to never fail while something attached to it (usually hardware) may.

A couple of OS have been released which claim to be mathematically provable that they behave as expected (unlike Windows), a critical step in providing truly error free software.

Nevertheless, I still hold that software can be bug free (not the way most people develop though).

I once read some works from a guy who was adamant that software can be 100% bug free and there&#039;s no reason not to strive for it, but I can&#039;t remember his name and I stumbled here looking for it again.

You may do well to familiarize yourself with the Unix software development ideology. If think link will go through, it might at least help you decrease the amount of bugs in your software:
http://c2.com/cgi-bin/wiki?UnitTest</description>
		<content:encoded><![CDATA[<p>I actually believe that software can be 100% bug free; or at least 99.99%.</p>
<p>And in an attempt to discredit the possibility, Johnson above, provided a list of examples which unfortunately do not exhibit the same nature as software and accordingly does not hold water.</p>
<p>Unlike his examples, software is not subject to degradation (or is capable of not being so) or mechanical failures. This is not to say that a software-driven system will never exhibit &#8220;problems&#8221; but that the software has the propensity to never fail while something attached to it (usually hardware) may.</p>
<p>A couple of OS have been released which claim to be mathematically provable that they behave as expected (unlike Windows), a critical step in providing truly error free software.</p>
<p>Nevertheless, I still hold that software can be bug free (not the way most people develop though).</p>
<p>I once read some works from a guy who was adamant that software can be 100% bug free and there&#8217;s no reason not to strive for it, but I can&#8217;t remember his name and I stumbled here looking for it again.</p>
<p>You may do well to familiarize yourself with the Unix software development ideology. If think link will go through, it might at least help you decrease the amount of bugs in your software:<br />
<a href="http://c2.com/cgi-bin/wiki?UnitTest" rel="nofollow">http://c2.com/cgi-bin/wiki?UnitTest</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: raspnortantem</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-32184</link>
		<dc:creator>raspnortantem</dc:creator>
		<pubDate>Fri, 16 Jan 2009 02:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-32184</guid>
		<description>Hello guys and girls!

I&#039;m a newbie here.

So i&#039;d like to know  if a world financial crisis affected someone among you?</description>
		<content:encoded><![CDATA[<p>Hello guys and girls!</p>
<p>I&#8217;m a newbie here.</p>
<p>So i&#8217;d like to know  if a world financial crisis affected someone among you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-10236</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 21 Nov 2007 15:34:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-10236</guid>
		<description>Even after software deployment I recommend sending detailed error reports in case of errors/bugs.  There are different tools that enable you to do this. (eg Eurekalog..)</description>
		<content:encoded><![CDATA[<p>Even after software deployment I recommend sending detailed error reports in case of errors/bugs.  There are different tools that enable you to do this. (eg Eurekalog..)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-4930</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 20 Jul 2007 06:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-4930</guid>
		<description>Maybe R. Cruz can enlighten us about what he sees as the best Development Tools?</description>
		<content:encoded><![CDATA[<p>Maybe R. Cruz can enlighten us about what he sees as the best Development Tools?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R Cruz</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-4367</link>
		<dc:creator>R Cruz</dc:creator>
		<pubDate>Mon, 25 Jun 2007 19:31:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-4367</guid>
		<description>Just I will add a point, select your development tools properly. As many bugs will come from your development platform. Incorrect or bug in the compiler, that are not addressed by the manufacturer.

We discovered that a bug free code can be a night mare on a totally crapy developer platform, when the right platform is used no bugs.</description>
		<content:encoded><![CDATA[<p>Just I will add a point, select your development tools properly. As many bugs will come from your development platform. Incorrect or bug in the compiler, that are not addressed by the manufacturer.</p>
<p>We discovered that a bug free code can be a night mare on a totally crapy developer platform, when the right platform is used no bugs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Muys</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-4357</link>
		<dc:creator>Peter Muys</dc:creator>
		<pubDate>Mon, 25 Jun 2007 01:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-4357</guid>
		<description>+1000 for user reporting and feedback.

After adding user feedback and error reporting to my application, I found some bugs I myself would never have found. 

Should have added this from the beginning...</description>
		<content:encoded><![CDATA[<p>+1000 for user reporting and feedback.</p>
<p>After adding user feedback and error reporting to my application, I found some bugs I myself would never have found. </p>
<p>Should have added this from the beginning&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C Johnson</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-4353</link>
		<dc:creator>C Johnson</dc:creator>
		<pubDate>Sun, 24 Jun 2007 22:16:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-4353</guid>
		<description>People like to think that bugs are limited to software, but truely, it extends to other things as well.

Ever hit your thumb with a hammer?  I&#039;d call that a glitch derived from a design flaw.  Gun misfire? Car need continual maintenance and even service packs (factory recalls to install safety equipment), even upgrades and options.  Consider public transit the open source version (which provides a great parallel to other open source projects on many levels).

So yes, bug free is a myth started by those who assume that the devices around them work flawlessly when it just isn&#039;t true.  Speaking of which, I have to go debug my lawn, it keeps overflowing...</description>
		<content:encoded><![CDATA[<p>People like to think that bugs are limited to software, but truely, it extends to other things as well.</p>
<p>Ever hit your thumb with a hammer?  I&#8217;d call that a glitch derived from a design flaw.  Gun misfire? Car need continual maintenance and even service packs (factory recalls to install safety equipment), even upgrades and options.  Consider public transit the open source version (which provides a great parallel to other open source projects on many levels).</p>
<p>So yes, bug free is a myth started by those who assume that the devices around them work flawlessly when it just isn&#8217;t true.  Speaking of which, I have to go debug my lawn, it keeps overflowing&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
