<?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: Neuroprosthetics</title>
	<atom:link href="http://techlifepost.com/2009/01/21/neuroprosthetics/feed/" rel="self" type="application/rss+xml" />
	<link>http://techlifepost.com/2009/01/21/neuroprosthetics/</link>
	<description>Living with technology.</description>
	<lastBuildDate>Fri, 20 Jan 2012 02:22:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Zoe Brain</title>
		<link>http://techlifepost.com/2009/01/21/neuroprosthetics/comment-page-1/#comment-266</link>
		<dc:creator>Zoe Brain</dc:creator>
		<pubDate>Mon, 26 Jan 2009 01:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://techlifepost.com/?p=2355#comment-266</guid>
		<description>As a software engineer who works in aerospace and making medical therapeutic devices (and naval combat systems etc)... Eric, I agree with you wholeheartedly.

The problem seems to be that a buggy, poorly-engineered piece of used food that&#039;s ready in June will always outsell a reliable, easy to use and flexible system that won&#039;t be ready until September. In fact, it will monopolise the market, so the second system never gets a look-in. 
That in turn is replaced with an even more buggy system with more bells and whistles in December. And so it goes.

Or it does unless lives are at stake, and/or lawsuits likely unless engineering best practices are used.

The thing is, these engineering best practices have now been developed in aerospace in particular so that there&#039;s no longer a time penalty till delivery. Unfortunately, the number of aerospace practioners is small, and the supply of MSCE&#039;s far greater, so from a human resources viewpoint, it makes sense to continue with shoddy development. Instead of fault-tolerant systems, we have created fault-tolerant customers - even in the military now.</description>
		<content:encoded><![CDATA[<p>As a software engineer who works in aerospace and making medical therapeutic devices (and naval combat systems etc)&#8230; Eric, I agree with you wholeheartedly.</p>
<p>The problem seems to be that a buggy, poorly-engineered piece of used food that&#8217;s ready in June will always outsell a reliable, easy to use and flexible system that won&#8217;t be ready until September. In fact, it will monopolise the market, so the second system never gets a look-in.<br />
That in turn is replaced with an even more buggy system with more bells and whistles in December. And so it goes.</p>
<p>Or it does unless lives are at stake, and/or lawsuits likely unless engineering best practices are used.</p>
<p>The thing is, these engineering best practices have now been developed in aerospace in particular so that there&#8217;s no longer a time penalty till delivery. Unfortunately, the number of aerospace practioners is small, and the supply of MSCE&#8217;s far greater, so from a human resources viewpoint, it makes sense to continue with shoddy development. Instead of fault-tolerant systems, we have created fault-tolerant customers &#8211; even in the military now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Jacksch</title>
		<link>http://techlifepost.com/2009/01/21/neuroprosthetics/comment-page-1/#comment-265</link>
		<dc:creator>Eric Jacksch</dc:creator>
		<pubDate>Sun, 25 Jan 2009 19:07:58 +0000</pubDate>
		<guid isPermaLink="false">http://techlifepost.com/?p=2355#comment-265</guid>
		<description>With the exception of a few fields (like aerospace and some medical devices), software today is often so poorly designed.  Very little, if any, &quot;engineering&quot; goes into most &quot;software engineering&quot;.</description>
		<content:encoded><![CDATA[<p>With the exception of a few fields (like aerospace and some medical devices), software today is often so poorly designed.  Very little, if any, &#8220;engineering&#8221; goes into most &#8220;software engineering&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://techlifepost.com/2009/01/21/neuroprosthetics/comment-page-1/#comment-260</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 23 Jan 2009 19:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://techlifepost.com/?p=2355#comment-260</guid>
		<description>Interesting!  I&#039;ve been wondering what happened since seeing a few news reports about artificial synapses years ago.</description>
		<content:encoded><![CDATA[<p>Interesting!  I&#8217;ve been wondering what happened since seeing a few news reports about artificial synapses years ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Kellogg</title>
		<link>http://techlifepost.com/2009/01/21/neuroprosthetics/comment-page-1/#comment-256</link>
		<dc:creator>Alan Kellogg</dc:creator>
		<pubDate>Fri, 23 Jan 2009 16:11:31 +0000</pubDate>
		<guid isPermaLink="false">http://techlifepost.com/?p=2355#comment-256</guid>
		<description>Our attitude towards programming and malware will have to change, once mistakes and malignancy become literally matters of life, death, and free will. Getting it right and getting it complete is going to be vital again.</description>
		<content:encoded><![CDATA[<p>Our attitude towards programming and malware will have to change, once mistakes and malignancy become literally matters of life, death, and free will. Getting it right and getting it complete is going to be vital again.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

