<?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: Designed to Fail</title>
	<atom:link href="/?feed=rss2&#038;p=48" rel="self" type="application/rss+xml" />
	<link>https://zuschlogin.com/?p=48</link>
	<description>Human factors, human-computer interface, GUI design, and usability engineering pondered monthly by Michael Zuschlag</description>
	<lastBuildDate>Thu, 24 May 2012 13:11:51 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Bachman</title>
		<link>https://zuschlogin.com/?p=48&#038;cpage=1#comment-774</link>
		<dc:creator>Mike Bachman</dc:creator>
		<pubDate>Sun, 07 Jun 2009 02:25:17 +0000</pubDate>
		<guid isPermaLink="false">https://zuschlogin.com/?p=48#comment-774</guid>
		<description>Zee

I have often thought about this problem.  HW designers have fixed this issue quite well.. Its called the IC and the Schematic.  The IC is designed and tested and has a few or sometime many features... bu tthes efeatures are FIXED and therefore can be readily tested and perfected.. even an IC as complex as as a DSP or DualCore has been fully run through tests.. and these tests are standardized as a fully tested to catch bugs..

ICs come with spec sheets and you can look throug the specs and pick the ones that world best.  And these spec sheets confomr to a basic standard.

And thenm you put them all together in a schematic.. something everyone can read and quickly understand

Why this doesn&#039;t work for the SW world, IMHO, is that SW dudes like to mess wit h everything.. they get a DLL or open suorce module, that may well ne 100% perfect.. but they tweek it so it is &quot;better&quot;... A HW guy CAN&quot;T tweek the IC, he uses it as is. with all its limitations.. he just uses it.  SW guys don&#039;t do that.. they chnage everything and thus everything is suspect.. and there has never been a good schematic for SW..

Find these solutions and SW will become as easy as HW is now... thiung back 30 yeasr and how hard it was to build a working computer.. now it is on one chip.. power it up and it works 100% perfectly.. very time..  Treat SW like HW and 20 years from now we will finally have SW that works....</description>
		<content:encoded><![CDATA[<p>Zee</p>
<p>I have often thought about this problem.  HW designers have fixed this issue quite well.. Its called the IC and the Schematic.  The IC is designed and tested and has a few or sometime many features&#8230; bu tthes efeatures are FIXED and therefore can be readily tested and perfected.. even an IC as complex as as a DSP or DualCore has been fully run through tests.. and these tests are standardized as a fully tested to catch bugs..</p>
<p>ICs come with spec sheets and you can look throug the specs and pick the ones that world best.  And these spec sheets confomr to a basic standard.</p>
<p>And thenm you put them all together in a schematic.. something everyone can read and quickly understand</p>
<p>Why this doesn&#8217;t work for the SW world, IMHO, is that SW dudes like to mess wit h everything.. they get a DLL or open suorce module, that may well ne 100% perfect.. but they tweek it so it is &#8220;better&#8221;&#8230; A HW guy CAN&#8221;T tweek the IC, he uses it as is. with all its limitations.. he just uses it.  SW guys don&#8217;t do that.. they chnage everything and thus everything is suspect.. and there has never been a good schematic for SW..</p>
<p>Find these solutions and SW will become as easy as HW is now&#8230; thiung back 30 yeasr and how hard it was to build a working computer.. now it is on one chip.. power it up and it works 100% perfectly.. very time..  Treat SW like HW and 20 years from now we will finally have SW that works&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
