<?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: MNteractive Profile: Refactr</title>
	<atom:link href="http://mnteractive.com/archive/mnteractive-profile-refactr/feed" rel="self" type="application/rss+xml" />
	<link>http://mnteractive.com/archive/mnteractive-profile-refactr</link>
	<description>Minnesota's Interaction Design, Information Architecture, and User Experience Design Community</description>
	<lastBuildDate>Thu, 25 Feb 2010 14:19:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harlin Jones</title>
		<link>http://mnteractive.com/archive/mnteractive-profile-refactr/comment-page-1#comment-3877</link>
		<dc:creator>Harlin Jones</dc:creator>
		<pubDate>Tue, 27 Feb 2007 17:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://mnteractive.com/archive/mnteractive-profile-refactr/#comment-3877</guid>
		<description>It&#039;s great to hear about a small group of sharp developers going the agile route, and it&#039;s especially cool to hear about their use of Grails.  

I do have one small suggestion that could make for a better podcast.  It comes off as somewhat awkward to hear the interviewees&#039; responses to the questions without hearing the actual questions.  The listener has to guess the context of each response.  So, let&#039;s hear both sides on the conversation next time.  Doing so should transform a decent podcast into a good one.</description>
		<content:encoded><![CDATA[<p>It&#8217;s great to hear about a small group of sharp developers going the agile route, and it&#8217;s especially cool to hear about their use of Grails.  </p>
<p>I do have one small suggestion that could make for a better podcast.  It comes off as somewhat awkward to hear the interviewees&#8217; responses to the questions without hearing the actual questions.  The listener has to guess the context of each response.  So, let&#8217;s hear both sides on the conversation next time.  Doing so should transform a decent podcast into a good one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
