<?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: How The Paradox of Choice Influences Software</title>
	<atom:link href="http://www.codesqueeze.com/how-the-paradox-of-choice-influences-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codesqueeze.com/how-the-paradox-of-choice-influences-software/</link>
	<description>Ideas for building efficient developers and software</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:03:44 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: ActiveEngine Sensei</title>
		<link>http://www.codesqueeze.com/how-the-paradox-of-choice-influences-software/#comment-1009</link>
		<dc:creator>ActiveEngine Sensei</dc:creator>
		<pubDate>Thu, 31 Jan 2008 11:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/how-the-paradox-of-choice-influences-software/#comment-1009</guid>
		<description>UGGHhhh!!  Sorry for the misspellings in comments - it&#039;s too early to write!!</description>
		<content:encoded><![CDATA[<p>UGGHhhh!!  Sorry for the misspellings in comments &#8211; it&#8217;s too early to write!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ActiveEngine Sensei</title>
		<link>http://www.codesqueeze.com/how-the-paradox-of-choice-influences-software/#comment-1008</link>
		<dc:creator>ActiveEngine Sensei</dc:creator>
		<pubDate>Thu, 31 Jan 2008 11:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/how-the-paradox-of-choice-influences-software/#comment-1008</guid>
		<description>I agree that .Net should not try to out the offerings from the Java side.  Too many choices often kills ingenuity since you travel down the valley of analysis paralysis.  That said, I think .Net developers adopting design patterns that have been more prevalent in use in the Java world is a good thing.  When you think about it, the design patterns are about confining your solution to a smaller set of choices - a pattern by definition is a directed path, limiting your choices.

W. Edwards Demming once said that second entrant into a market stands a much better chance of crushing competition since they will innovate and improve, as opposed to invent.</description>
		<content:encoded><![CDATA[<p>I agree that .Net should not try to out the offerings from the Java side.  Too many choices often kills ingenuity since you travel down the valley of analysis paralysis.  That said, I think .Net developers adopting design patterns that have been more prevalent in use in the Java world is a good thing.  When you think about it, the design patterns are about confining your solution to a smaller set of choices &#8211; a pattern by definition is a directed path, limiting your choices.</p>
<p>W. Edwards Demming once said that second entrant into a market stands a much better chance of crushing competition since they will innovate and improve, as opposed to invent.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

