<?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"
	>
<channel>
	<title>Comments on: When does refactoring become something&#160;more?</title>
	<atom:link href="http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/</link>
	<description>Sam Newman's blog</description>
	<pubDate>Fri, 08 Aug 2008 19:08:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Abdel A Saleh</title>
		<link>http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/#comment-515</link>
		<dc:creator>Abdel A Saleh</dc:creator>
		<pubDate>Wed, 15 Sep 2004 15:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/09/09/when-does-refactoring-become-something-more/#comment-515</guid>
		<description>Hi, 

I have to agree with Franz. In many instances where there is no tool to aid in automating a refactoring, the task (of refactoring) does take a fair bit of time, ie more than 10 minutes. But it is still a refactoring..
</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>I have to agree with Franz. In many instances where there is no tool to aid in automating a refactoring, the task (of refactoring) does take a fair bit of time, <acronym title="Internet Explorer">IE</acronym> more than 10 minutes. But it is still a refactoring..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/#comment-514</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Sun, 12 Sep 2004 11:48:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/09/09/when-does-refactoring-become-something-more/#comment-514</guid>
		<description>Perhaps what I should of said is not "is something that takes more than X a refactoring" but more "is a refactoring that takes more than X something we should do"?</description>
		<content:encoded><![CDATA[<p>Perhaps what I should of said is not &#8220;is something that takes more than X a refactoring&#8221; but more &#8220;is a refactoring that takes more than X something we should do&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: franz</title>
		<link>http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/#comment-513</link>
		<dc:creator>franz</dc:creator>
		<pubDate>Sat, 11 Sep 2004 17:57:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/09/09/when-does-refactoring-become-something-more/#comment-513</guid>
		<description>every task that keeps the algorithm the same and just change the overall structure. i.e. class, method, parameter, field, variable etc... IS A REFACTORING. 
The duration of the refactoring mainly rely to the automation of it. 
Find and factorize duplicate code is a next refactoring task to be automated (Intellij already contains plugin in order to help in this task). 
That it, that's all. Don't try to complexify the refactoring meaning with duration please!!!</description>
		<content:encoded><![CDATA[<p>every task that keeps the algorithm the same and just change the overall structure. i.e. class, method, parameter, field, variable etc&#8230; IS A REFACTORING. <br />
The duration of the refactoring mainly rely to the automation of it. <br />
Find and factorize duplicate code is a next refactoring task to be automated (Intellij already contains plugin in order to help in this task). <br />
That it, that&#8217;s all. Don&#8217;t try to complexify the refactoring meaning with duration please!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/#comment-512</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Thu, 09 Sep 2004 20:59:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/09/09/when-does-refactoring-become-something-more/#comment-512</guid>
		<description>We left it in as it did improve the code we wrote. We actually took another look at the original problem after a break and managed to fix it, so replacing all duplications.

There is certainly a tradeoff between being consistently wrong and inconsistently right, and doing the best thing at the time - coding in the right way for the task at hand, where applying the 'correct' code across the codebase would involve significant effort (beyond the scope of what could be thought of as refactoring).</description>
		<content:encoded><![CDATA[<p>We left it in as it did improve the code we wrote. We actually took another look at the original problem after a break and managed to fix it, so replacing all duplications.</p>
<p>There is certainly a tradeoff between being consistently wrong and inconsistently right, and doing the best thing at the time &#8211; coding in the right way for the task at hand, where applying the &#8216;correct&#8217; code across the codebase would involve significant effort (beyond the scope of what could be thought of as refactoring).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ade</title>
		<link>http://www.magpiebrain.com/blog/2004/09/09/when-does-refactoring-become-something-more/#comment-511</link>
		<dc:creator>ade</dc:creator>
		<pubDate>Thu, 09 Sep 2004 16:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/09/09/when-does-refactoring-become-something-more/#comment-511</guid>
		<description>Did you back out your changes or did you leave the codebase with some code using the visitor and some code doing it the old way?
I think we need a word for the kind of variegated code that results when people use the time a refactoring will take as a reason to only partially apply a change. Maybe it's better to accept the duplication rather than introduce variegation--code with many different ways of doing the same thing.</description>
		<content:encoded><![CDATA[<p>Did you back out your changes or did you leave the codebase with some code using the visitor and some code doing it the old way?<br />
I think we need a word for the kind of variegated code that results when people use the time a refactoring will take as a reason to only partially apply a change. Maybe it&#8217;s better to accept the duplication rather than introduce variegation&#8212;code with many different ways of doing the same thing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
