<?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: The importance of failing quickly and often</title>
	<atom:link href="http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/</link>
	<description>Shedding Light on the Hidden World of Embedded Systems</description>
	<lastBuildDate>Mon, 28 Jul 2014 16:18:37 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: A.F. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/#comment-4492</link>
		<dc:creator>A.F. @ LI</dc:creator>
		<pubDate>Sat, 11 Dec 2010 02:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=394#comment-4492</guid>
		<description>An interesting point raised in the article is the misuse of planning for the resolution of unstructured problems. A hidden assumption by those doing the planning is that they have &quot;perfect knowledge&quot; of the problem domain. In embedded software or any other software realm for that matter, such an assumption is misleading at best and delusional at worst. I&#039;ve seen far too many well crafted &quot;plans&quot; go off the rails because of unanticipated problems. Unfortunately in today&#039;s corporate world, you won&#039;t get the go ahead for a project unless you have a plan, hence the use of hedging and hidden contingencies in the schedule.</description>
		<content:encoded><![CDATA[<p>An interesting point raised in the article is the misuse of planning for the resolution of unstructured problems. A hidden assumption by those doing the planning is that they have &#8220;perfect knowledge&#8221; of the problem domain. In embedded software or any other software realm for that matter, such an assumption is misleading at best and delusional at worst. I&#8217;ve seen far too many well crafted &#8220;plans&#8221; go off the rails because of unanticipated problems. Unfortunately in today&#8217;s corporate world, you won&#8217;t get the go ahead for a project unless you have a plan, hence the use of hedging and hidden contingencies in the schedule.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A.N. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/#comment-4491</link>
		<dc:creator>A.N. @ LI</dc:creator>
		<pubDate>Sat, 11 Dec 2010 02:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=394#comment-4491</guid>
		<description>Instead of &quot;business school graduates&quot;, it would be interesting to see how Engineers perform - you&#039;ve already hinted that Engineers are also more likely to adopt an interative, prototyping approach.

It would also be interesting to compare how recent engineering graduates compare with experienced engineers.

A very disappointingly large number of posts on internet forums are along the lines of. &quot;I wrote this code and it doesn&#039;t work. What&#039;s wrong?&quot;
There is no attempt at analysing what, exactly, is &quot;wrong&quot; - it should be obvious that this is an essential precursor to fixing the problem, but simply doesn&#039;t seem to occur to the posters!

The important thing is not that you fail, but that you can analyse the reasons for failure - and do better next time!</description>
		<content:encoded><![CDATA[<p>Instead of &#8220;business school graduates&#8221;, it would be interesting to see how Engineers perform &#8211; you&#8217;ve already hinted that Engineers are also more likely to adopt an interative, prototyping approach.</p>
<p>It would also be interesting to compare how recent engineering graduates compare with experienced engineers.</p>
<p>A very disappointingly large number of posts on internet forums are along the lines of. &#8220;I wrote this code and it doesn&#8217;t work. What&#8217;s wrong?&#8221;<br />
There is no attempt at analysing what, exactly, is &#8220;wrong&#8221; &#8211; it should be obvious that this is an essential precursor to fixing the problem, but simply doesn&#8217;t seem to occur to the posters!</p>
<p>The important thing is not that you fail, but that you can analyse the reasons for failure &#8211; and do better next time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I.B. @ LI</title>
		<link>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/#comment-4485</link>
		<dc:creator>I.B. @ LI</dc:creator>
		<pubDate>Thu, 09 Dec 2010 16:10:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=394#comment-4485</guid>
		<description>Thanks for pointing on the Embedded Insights - it&#039;s the interesting resource.</description>
		<content:encoded><![CDATA[<p>Thanks for pointing on the Embedded Insights &#8211; it&#8217;s the interesting resource.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Titus</title>
		<link>http://www.embeddedinsights.com/channels/2010/12/03/the-importance-of-failing-quickly-and-often/#comment-4411</link>
		<dc:creator>Jon Titus</dc:creator>
		<pubDate>Sat, 04 Dec 2010 17:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.embeddedinsights.com/channels/?p=394#comment-4411</guid>
		<description>Kids in kindergarten also feel less peer pressure that people with MBAs, to they&#039;re likely to try many things that might seem &quot;dumb&quot; to people with more education.</description>
		<content:encoded><![CDATA[<p>Kids in kindergarten also feel less peer pressure that people with MBAs, to they&#8217;re likely to try many things that might seem &#8220;dumb&#8221; to people with more education.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
