<?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: Scott Diedrick &#8211; Profiles in Courage &#8211; RedMonk Radio 058</title>
	<atom:link href="http://www.redmonk.com/cote/2009/03/30/redmonkradio058/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/cote/2009/03/30/redmonkradio058/</link>
	<description>One foot in the muck, the other in utopia</description>
	<lastBuildDate>Thu, 24 May 2012 14:45:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Mike Lunt</title>
		<link>http://www.redmonk.com/cote/2009/03/30/redmonkradio058/comment-page-1/#comment-309821</link>
		<dc:creator>Mike Lunt</dc:creator>
		<pubDate>Mon, 30 Mar 2009 13:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/cote/2009/03/30/redmonkradio058/#comment-309821</guid>
		<description>Nice recording...  I almost cried when I thought Scott was saying they went from 2 week to 1 month iterations to tackle big features, but instead, the Mumboe team holds true to the &quot;stay releasable&quot; concept and continues with the 2 week iterations.  
 
One interesting point on the use of interpreted languages in this context is that they provide a lot of the same benefit that SaaS products provide in terms of giving customers patches sooner.  With Ruby and Python COTS, support people can often apply a fix on the customer&#039;s box (or the hosted server in the case of SaaS) with very little risk.  Granted, I&#039;m mixing languages and delivery mechanisms, but the point is that COTS products based on compiled languages often lose the patching battle because it&#039;s so hard to deliver a low-risk fix. 
 
...end of rambling.  :-) </description>
		<content:encoded><![CDATA[<p>Nice recording&#8230;  I almost cried when I thought Scott was saying they went from 2 week to 1 month iterations to tackle big features, but instead, the Mumboe team holds true to the &quot;stay releasable&quot; concept and continues with the 2 week iterations. </p>
<p>One interesting point on the use of interpreted languages in this context is that they provide a lot of the same benefit that SaaS products provide in terms of giving customers patches sooner.  With Ruby and Python COTS, support people can often apply a fix on the customer&#039;s box (or the hosted server in the case of SaaS) with very little risk.  Granted, I&#039;m mixing languages and delivery mechanisms, but the point is that COTS products based on compiled languages often lose the patching battle because it&#039;s so hard to deliver a low-risk fix.</p>
<p>&#8230;end of rambling.  :-) </p>
]]></content:encoded>
	</item>
</channel>
</rss>

