<?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>Wed, 18 Jan 2012 21:41:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Research FIrst</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-131663</link>
		<dc:creator>Research FIrst</dc:creator>
		<pubDate>Sat, 08 Oct 2011 14:44:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-131663</guid>
		<description>only the Worst programmer in python use print statements , 80% of python programmers uses logging module, and its built in. Go read some popular python software code and come tell me how many uses print , for debugging.</description>
		<content:encoded><![CDATA[<p>only the Worst programmer in python use print statements , 80% of python programmers uses logging module, and its built in. Go read some popular python software code and come tell me how many uses print , for debugging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Research FIrst</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-131661</link>
		<dc:creator>Research FIrst</dc:creator>
		<pubDate>Sat, 08 Oct 2011 14:39:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-131661</guid>
		<description>Wait why you said that there&#039;s no good debugger for python?

Python have very good built in debugger . Pydev&#039;s debugger is Super Awesome and for those Eclipse haters winpdb.org is most powerful debugger i ever used.

Unit test if freaking easy to write in python with its own unittest mnodule. And python have built-in logging module which is on par with java one . And using ipython  , it becomes totally test dirven approach.

Please research more first.</description>
		<content:encoded><![CDATA[<p>Wait why you said that there&#8217;s no good debugger for python?</p>
<p>Python have very good built in debugger . Pydev&#8217;s debugger is Super Awesome and for those Eclipse haters winpdb.org is most powerful debugger i ever used.</p>
<p>Unit test if freaking easy to write in python with its own unittest mnodule. And python have built-in logging module which is on par with java one . And using ipython  , it becomes totally test dirven approach.</p>
<p>Please research more first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amarjeet Chavhan</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-122362</link>
		<dc:creator>Amarjeet Chavhan</dc:creator>
		<pubDate>Fri, 29 Jul 2011 04:26:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-122362</guid>
		<description>All are the known facts, but many time Schedule does not allow to follow this process.. If you are looking for bug free application then u must follow this…</description>
		<content:encoded><![CDATA[<p>All are the known facts, but many time Schedule does not allow to follow this process.. If you are looking for bug free application then u must follow this…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/comment-page-1/#comment-104910</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Tue, 22 Mar 2011 13:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/postings/12-practical-tips-for-building-bug-free-software/262/#comment-104910</guid>
		<description>What amazes me is that lots of people seem - or at least claim - to know the root cause of the problem, the remedy and the so-called &quot;solution&quot;. Yet, most of the software in the market is buggy, often to be point of being unusable (in the first couple of versions at least).

If indeed any of these solutions is anything but someone&#039;s personal brand of snake-oil, how do we find out which one it is? Has anyone created creating bug-free software? Or even come close to it? The closest I have heard of to a real-life bug-free software is the one used in the space shuttles. But that software costs a few thousands of dollars per LINE of code.

Forgive my skepticism please, but I don&#039;t believe any of these solutions achieve anything beyond surface scratching. People trot out common sense advice - make sure the design is good, spend a lot of time testing it, and so forth - but there is nothing of substance there. A TRULY good design will cost a huge amount of money, resources, time, and work, and to that extent, is IMPRACTICAL in a real-life situation, where one is constantly faced with a shortage of time, money, and resources.

So advice like this is useless, one way or another.</description>
		<content:encoded><![CDATA[<p>What amazes me is that lots of people seem &#8211; or at least claim &#8211; to know the root cause of the problem, the remedy and the so-called &#8220;solution&#8221;. Yet, most of the software in the market is buggy, often to be point of being unusable (in the first couple of versions at least).</p>
<p>If indeed any of these solutions is anything but someone&#8217;s personal brand of snake-oil, how do we find out which one it is? Has anyone created creating bug-free software? Or even come close to it? The closest I have heard of to a real-life bug-free software is the one used in the space shuttles. But that software costs a few thousands of dollars per LINE of code.</p>
<p>Forgive my skepticism please, but I don&#8217;t believe any of these solutions achieve anything beyond surface scratching. People trot out common sense advice &#8211; make sure the design is good, spend a lot of time testing it, and so forth &#8211; but there is nothing of substance there. A TRULY good design will cost a huge amount of money, resources, time, and work, and to that extent, is IMPRACTICAL in a real-life situation, where one is constantly faced with a shortage of time, money, and resources.</p>
<p>So advice like this is useless, one way or another.</p>
]]></content:encoded>
	</item>
	<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>
</channel>
</rss>

