<?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: What does refactoring really mean?</title>
	<atom:link href="http://UnhinderedByTalent.com/Phi/archives/2007/10/01/what-does-refactoring-really-mean/feed/" rel="self" type="application/rss+xml" />
	<link>http://UnhinderedByTalent.com/Phi/archives/2007/10/01/what-does-refactoring-really-mean/</link>
	<description>Not all battles are fought with a sword</description>
	<lastBuildDate>Tue, 12 Jul 2011 20:09:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Phi</title>
		<link>http://UnhinderedByTalent.com/Phi/archives/2007/10/01/what-does-refactoring-really-mean/comment-page-1/#comment-30795</link>
		<dc:creator>Phi</dc:creator>
		<pubDate>Wed, 03 Oct 2007 20:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://UnhinderedByTalent.com/Phi/?p=659#comment-30795</guid>
		<description>I do &lt;em&gt;totally&lt;/em&gt; recommend Fowler&#039;s book.  I think the first five chapters (everything up to the big list of recipes that forms the bulk of the book) are as fine a piece of writing on programming out there, and totally worth the price of admission on their own.  Totally changed the way I think about programming.

I like your comment about refactoring helping move goodness when requirements change.  Change is when so much code begins to degrade, and refactoring gives you tools to help you maintain the quality of your system as you move in that new direction.  Even cooler, it opens up the doors to even make improvements while you&#039;re doing it, especially since you probably understand your code better having had more experience with it.

Good luck with the book!</description>
		<content:encoded><![CDATA[<p>I do <em>totally</em> recommend Fowler&#8217;s book.  I think the first five chapters (everything up to the big list of recipes that forms the bulk of the book) are as fine a piece of writing on programming out there, and totally worth the price of admission on their own.  Totally changed the way I think about programming.</p>
<p>I like your comment about refactoring helping move goodness when requirements change.  Change is when so much code begins to degrade, and refactoring gives you tools to help you maintain the quality of your system as you move in that new direction.  Even cooler, it opens up the doors to even make improvements while you&#8217;re doing it, especially since you probably understand your code better having had more experience with it.</p>
<p>Good luck with the book!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Krueger</title>
		<link>http://UnhinderedByTalent.com/Phi/archives/2007/10/01/what-does-refactoring-really-mean/comment-page-1/#comment-30793</link>
		<dc:creator>Alan Krueger</dc:creator>
		<pubDate>Wed, 03 Oct 2007 19:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://UnhinderedByTalent.com/Phi/?p=659#comment-30793</guid>
		<description>First, I haven&#039;t read the book, but not because I haven&#039;t wanted to.  I just haven&#039;t had the opportunity yet.

From my perspective, refactoring isn&#039;t just for moving from bad code to good code.  It&#039;s also critical in an agile environment for moving from previously-good code to newly-good code when requirements change.

Reading the linked article has made me move reading Refactoring up the priority list.</description>
		<content:encoded><![CDATA[<p>First, I haven&#8217;t read the book, but not because I haven&#8217;t wanted to.  I just haven&#8217;t had the opportunity yet.</p>
<p>From my perspective, refactoring isn&#8217;t just for moving from bad code to good code.  It&#8217;s also critical in an agile environment for moving from previously-good code to newly-good code when requirements change.</p>
<p>Reading the linked article has made me move reading Refactoring up the priority list.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

