<?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: Maybe NASA could use some buggy software</title>
	<atom:link href="http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/</link>
	<description>The blog of John D. Cook</description>
	<lastBuildDate>Thu, 11 Mar 2010 17:04:21 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anon</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25710</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Sat, 10 Oct 2009 05:22:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25710</guid>
		<description>The space shuttle software certainly doesn&#039;t sound bug free to me! The routines that control the physical systems my be bug free but the system as a whole certainly sounds like it isn&#039;t. When you have ui that tells you things are off when they are on but it is too cost prohibitive to change them, so you have 200 pounds of errata and manuals does not sounds like a resounding software engineering feat to me. 

http://ocw.mit.edu/OcwWeb/Aeronautics-and-Astronautics/16-885JFall-2005/LectureNotes/detail/embed22.htm</description>
		<content:encoded><![CDATA[<p>The space shuttle software certainly doesn&#8217;t sound bug free to me! The routines that control the physical systems my be bug free but the system as a whole certainly sounds like it isn&#8217;t. When you have ui that tells you things are off when they are on but it is too cost prohibitive to change them, so you have 200 pounds of errata and manuals does not sounds like a resounding software engineering feat to me. </p>
<p><a href="http://ocw.mit.edu/OcwWeb/Aeronautics-and-Astronautics/16-885JFall-2005/LectureNotes/detail/embed22.htm" rel="nofollow">http://ocw.mit.edu/OcwWeb/Aeronautics-and-Astronautics/16-885JFall-2005/LectureNotes/detail/embed22.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joel8360</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25692</link>
		<dc:creator>joel8360</dc:creator>
		<pubDate>Fri, 09 Oct 2009 17:23:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25692</guid>
		<description>&quot;as the probability of bugs goes to zero, the development costs go to infinity. &quot;

If this is true, then you will be able to do one of the following:
 - beggar Knuth
 - establish your reputation as the man who found scads of bugs where Knuth found none.</description>
		<content:encoded><![CDATA[<p>&#8220;as the probability of bugs goes to zero, the development costs go to infinity. &#8221;</p>
<p>If this is true, then you will be able to do one of the following:<br />
 &#8211; beggar Knuth<br />
 &#8211; establish your reputation as the man who found scads of bugs where Knuth found none.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25674</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 09 Oct 2009 11:23:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25674</guid>
		<description>Andrew, good points. I don&#039;t disagree that perfect software is preferable to buggy software. But sometimes the realistic alternative to buggy software is no software, and sometimes buggy software is better than no software.

Your point about budget surplus is right on. The savings evaporates, so you might as well spend all you can get.</description>
		<content:encoded><![CDATA[<p>Andrew, good points. I don&#8217;t disagree that perfect software is preferable to buggy software. But sometimes the realistic alternative to buggy software is no software, and sometimes buggy software is better than no software.</p>
<p>Your point about budget surplus is right on. The savings evaporates, so you might as well spend all you can get.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew T.</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25673</link>
		<dc:creator>Andrew T.</dc:creator>
		<pubDate>Fri, 09 Oct 2009 11:08:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25673</guid>
		<description>Would you like it if the electronically controlled brake system on a train failed at the wrong time? Some software must be &quot;perfect&quot; - where human lives are at risk, this is especially true. Guess what, if you&#039;re the responsible party for software that maims or kills someone, you&#039;re liable, just like if an Engineering firm builds a structure that fails.

On the point of unmanned missions. In software, as with many other places, as soon as you save money, it&#039;s not viewed as a surplus - it&#039;s viewed as a place to cut the budget. So a mission that would cost $500M is done for $375M because of slightly lower quality code (they outsourced to MIT), that other $125M pretty much disappears, you didn&#039;t spend it, you don&#039;t keep it. And anyway, I honestly don&#039;t think that $250M of $500M goes to the software on these missions, I don&#039;t even think software contributes 25% of the cost of any of these missions.

A great article on the way NASA writes software:
http://www.fastcompany.com/magazine/06/writestuff.html</description>
		<content:encoded><![CDATA[<p>Would you like it if the electronically controlled brake system on a train failed at the wrong time? Some software must be &#8220;perfect&#8221; &#8211; where human lives are at risk, this is especially true. Guess what, if you&#8217;re the responsible party for software that maims or kills someone, you&#8217;re liable, just like if an Engineering firm builds a structure that fails.</p>
<p>On the point of unmanned missions. In software, as with many other places, as soon as you save money, it&#8217;s not viewed as a surplus &#8211; it&#8217;s viewed as a place to cut the budget. So a mission that would cost $500M is done for $375M because of slightly lower quality code (they outsourced to MIT), that other $125M pretty much disappears, you didn&#8217;t spend it, you don&#8217;t keep it. And anyway, I honestly don&#8217;t think that $250M of $500M goes to the software on these missions, I don&#8217;t even think software contributes 25% of the cost of any of these missions.</p>
<p>A great article on the way NASA writes software:<br />
<a href="http://www.fastcompany.com/magazine/06/writestuff.html" rel="nofollow">http://www.fastcompany.com/magazine/06/writestuff.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joff</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25647</link>
		<dc:creator>Joff</dc:creator>
		<pubDate>Fri, 09 Oct 2009 00:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25647</guid>
		<description>If it doubles the cost to go from 98% to 99%, but if that failure happens, the cost could be in the tens of billions of dollars (and human lives), then yes, it&#039;s probably worth it.</description>
		<content:encoded><![CDATA[<p>If it doubles the cost to go from 98% to 99%, but if that failure happens, the cost could be in the tens of billions of dollars (and human lives), then yes, it&#8217;s probably worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josef</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25644</link>
		<dc:creator>Josef</dc:creator>
		<pubDate>Thu, 08 Oct 2009 23:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25644</guid>
		<description>Whenever humans and machines cooperate the human should always be the weakest link. What it means is that the machine has to be far more reliable than the human. And it&#039;s up to us as  programmers to make that happen. Sure programmers make mistakes to. But we have the advantage that we can simulate our programs forwards, backward, up, down and through a model checker. We can&#039;t do that with human beings. Not yet, and hopefully never.</description>
		<content:encoded><![CDATA[<p>Whenever humans and machines cooperate the human should always be the weakest link. What it means is that the machine has to be far more reliable than the human. And it&#8217;s up to us as  programmers to make that happen. Sure programmers make mistakes to. But we have the advantage that we can simulate our programs forwards, backward, up, down and through a model checker. We can&#8217;t do that with human beings. Not yet, and hopefully never.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25642</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 08 Oct 2009 22:30:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25642</guid>
		<description>Your site is spitting out ugly errors if a person forgets to fill out the email</description>
		<content:encoded><![CDATA[<p>Your site is spitting out ugly errors if a person forgets to fill out the email</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25641</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 08 Oct 2009 22:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25641</guid>
		<description>Yes, I can see political reasons playing a huge factors. Do you think the government still inject funding if more and more mission failed?</description>
		<content:encoded><![CDATA[<p>Yes, I can see political reasons playing a huge factors. Do you think the government still inject funding if more and more mission failed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25629</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 08 Oct 2009 15:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25629</guid>
		<description>Jason: There are political reasons as well, as Norvig points out after the quote above. If you&#039;re just looking at successful missions per dollar, you might lower your quality standards. But politics isn&#039;t measured in missions per dollar. Politically, the cost of a failed mission is much greater than the benefit of a successful mission.</description>
		<content:encoded><![CDATA[<p>Jason: There are political reasons as well, as Norvig points out after the quote above. If you&#8217;re just looking at successful missions per dollar, you might lower your quality standards. But politics isn&#8217;t measured in missions per dollar. Politically, the cost of a failed mission is much greater than the benefit of a successful mission.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Dyer</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25627</link>
		<dc:creator>Jason Dyer</dc:creator>
		<pubDate>Thu, 08 Oct 2009 14:22:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25627</guid>
		<description>I interviewed once (didn&#039;t get the job) at a company that did firmware for aeronautics.

There are legal reasons why one can&#039;t just program normally as suggested above.</description>
		<content:encoded><![CDATA[<p>I interviewed once (didn&#8217;t get the job) at a company that did firmware for aeronautics.</p>
<p>There are legal reasons why one can&#8217;t just program normally as suggested above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Omar Gomez</title>
		<link>http://www.johndcook.com/blog/2009/10/08/nasa-buggy-software/comment-page-1/#comment-25626</link>
		<dc:creator>Omar Gomez</dc:creator>
		<pubDate>Thu, 08 Oct 2009 14:09:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3343#comment-25626</guid>
		<description>Nice post.

I&#039;ve always though we Software people are too much focused on technical aspects and forgot how important economics are.</description>
		<content:encoded><![CDATA[<p>Nice post.</p>
<p>I&#8217;ve always though we Software people are too much focused on technical aspects and forgot how important economics are.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
