<?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"
	>
<channel>
	<title>Comments on: EDA Standards</title>
	<atom:link href="http://www.chipdesignmag.com/bailey/2008/06/24/eda-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chipdesignmag.com/bailey/2008/06/24/eda-standards/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Wed, 07 Jan 2009 22:35:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ray Salemi</title>
		<link>http://www.chipdesignmag.com/bailey/2008/06/24/eda-standards/#comment-11</link>
		<dc:creator>Ray Salemi</dc:creator>
		<pubDate>Tue, 24 Jun 2008 15:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.chipdesignmag.com/bailey/?p=7#comment-11</guid>
		<description>The end comment of your panel is one that I often hear as an EDA guy.  One person will say, "Standards are a Good Thing."  Then everyone shouts "Hear! Hear!" and all eyes slowly turn to the EDA vendors sitting in the back of the room (the greedy lummoxes!)

However, I've found that the engineers's love of a standard methodology quickly slips away when they are actually presented with one.  This is because the proposed methodology is "too big" or "too small" or "too OOPy" or "not OOPy enough" or "too confusing" or "too simplistic" or "too open" or "too closed" or "too new" or "too old" and always "Not Invented Here."

I applaud your comment that the user community should let their voices be heard.  I wonder, though, if they will all say something that can result in a standard.</description>
		<content:encoded><![CDATA[<p>The end comment of your panel is one that I often hear as an EDA guy.  One person will say, &#8220;Standards are a Good Thing.&#8221;  Then everyone shouts &#8220;Hear! Hear!&#8221; and all eyes slowly turn to the EDA vendors sitting in the back of the room (the greedy lummoxes!)</p>
<p>However, I&#8217;ve found that the engineers&#8217;s love of a standard methodology quickly slips away when they are actually presented with one.  This is because the proposed methodology is &#8220;too big&#8221; or &#8220;too small&#8221; or &#8220;too OOPy&#8221; or &#8220;not OOPy enough&#8221; or &#8220;too confusing&#8221; or &#8220;too simplistic&#8221; or &#8220;too open&#8221; or &#8220;too closed&#8221; or &#8220;too new&#8221; or &#8220;too old&#8221; and always &#8220;Not Invented Here.&#8221;</p>
<p>I applaud your comment that the user community should let their voices be heard.  I wonder, though, if they will all say something that can result in a standard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
