<?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: Prevent technology blow-ups from killing your project</title>
	<atom:link href="http://www.udidahan.com/2008/02/27/prevent-technology-blow-ups-from-killing-your-project/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2008/02/27/prevent-technology-blow-ups-from-killing-your-project/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Sat, 11 Feb 2012 15:16:10 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Old School</title>
		<link>http://www.udidahan.com/2008/02/27/prevent-technology-blow-ups-from-killing-your-project/comment-page-1/#comment-18112</link>
		<dc:creator>Old School</dc:creator>
		<pubDate>Wed, 27 Feb 2008 15:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2008/02/27/prevent-technology-blow-ups-from-killing-your-project/#comment-18112</guid>
		<description>I love to try out new technology as much as the next guy, but I try to avoid using it in mission critical, production applications. After the technology is no longer new, then perhaps it will be time to refactor it into the app, or build out new apps using it.

By then, of course, most of the fingers will have already been lost by those young&#039;uns who seem to believe they have lots of fingers to lose, and us &quot;old school&quot; folks can safely put the &quot;old&quot; technology to good use.</description>
		<content:encoded><![CDATA[<p>I love to try out new technology as much as the next guy, but I try to avoid using it in mission critical, production applications. After the technology is no longer new, then perhaps it will be time to refactor it into the app, or build out new apps using it.</p>
<p>By then, of course, most of the fingers will have already been lost by those young&#8217;uns who seem to believe they have lots of fingers to lose, and us &#8220;old school&#8221; folks can safely put the &#8220;old&#8221; technology to good use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr_Simple</title>
		<link>http://www.udidahan.com/2008/02/27/prevent-technology-blow-ups-from-killing-your-project/comment-page-1/#comment-18100</link>
		<dc:creator>Mr_Simple</dc:creator>
		<pubDate>Wed, 27 Feb 2008 15:06:23 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2008/02/27/prevent-technology-blow-ups-from-killing-your-project/#comment-18100</guid>
		<description>In my opinion, mature developers - measured in projects shipped - have a the ability to intuitively &quot;smoke out&quot; these &quot;cool&quot; tools from the start and use &quot;old-school&quot; but tried and true methods.

Our methods are simple, but production proven strong and reliable.</description>
		<content:encoded><![CDATA[<p>In my opinion, mature developers &#8211; measured in projects shipped &#8211; have a the ability to intuitively &#8220;smoke out&#8221; these &#8220;cool&#8221; tools from the start and use &#8220;old-school&#8221; but tried and true methods.</p>
<p>Our methods are simple, but production proven strong and reliable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

