<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Legacy Code, Refactoring, and Ownership</title>
	<link>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/</link>
	<description>Incoherent and disjointed opinionated drivel from somewhere near London</description>
	<pubDate>Wed, 20 Aug 2008 10:30:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: CD</title>
		<link>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-567</link>
		<dc:creator>CD</dc:creator>
		<pubDate>Sun, 23 Mar 2008 11:25:17 +0000</pubDate>
		<guid>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-567</guid>
		<description>Refactoring isn't a pain in the boss?
i've  refactored terrible code from prolog to msx basic, then to msx basic II turbo, then to quick basic and to pascal.
I think i have enough bacground to discuss refactoring with my boss who actually fired me for trying to explain him what refactoring means.
Now i am a jobless .net programmer. wanna work with me? i take some time to refactor. when you work on legacy code your own brain refactors.!</description>
		<content:encoded><![CDATA[<p>Refactoring isn&#8217;t a pain in the boss?<br />
i&#8217;ve  refactored terrible code from prolog to msx basic, then to msx basic II turbo, then to quick basic and to pascal.<br />
I think i have enough bacground to discuss refactoring with my boss who actually fired me for trying to explain him what refactoring means.<br />
Now i am a jobless .net programmer. wanna work with me? i take some time to refactor. when you work on legacy code your own brain refactors.!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: russ</title>
		<link>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-5</link>
		<dc:creator>russ</dc:creator>
		<pubDate>Sat, 15 Dec 2007 21:43:07 +0000</pubDate>
		<guid>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-5</guid>
		<description>"After all, ‘terrible code’ is by definition any software code you yourself didn’t write. Right?"

Oh give it a rest, that's not what I said. Why have you put 'terrible code' in quote marks as if you're quoting me, when that phrase appears nowhere in the article? In fact, the whole point of the post is that there are benefits to refactoring beyond simply trying to improve code. You understood that, though. Right?</description>
		<content:encoded><![CDATA[<p>&#8220;After all, ‘terrible code’ is by definition any software code you yourself didn’t write. Right?&#8221;</p>
<p>Oh give it a rest, that&#8217;s not what I said. Why have you put &#8216;terrible code&#8217; in quote marks as if you&#8217;re quoting me, when that phrase appears nowhere in the article? In fact, the whole point of the post is that there are benefits to refactoring beyond simply trying to improve code. You understood that, though. Right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: russ</title>
		<link>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-4</link>
		<dc:creator>russ</dc:creator>
		<pubDate>Sat, 15 Dec 2007 21:28:02 +0000</pubDate>
		<guid>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-4</guid>
		<description>"I bring this to your attention so as not to continue the proliferation of mythology and mislead potentially innocent bystanders into a similar state of delusion."

The phrase "everyone knows that" was intended to be slightly tongue-in-cheek, which I had hoped would be picked up by being unnecessarily sweeping and all-encompassing. Generally speaking I think it's a good thing, but I also think Steve Yegge hit the nail on the head when he said that refactoring had become the &lt;a href="http://steve.yegge.googlepages.com/transformation" rel="nofollow"&gt;goal rather than the cure&lt;/a&gt;.

I read your &lt;a href="http://blog.tmorris.net/refunctoring/" rel="nofollow"&gt;Refunctoring&lt;/a&gt; article and largely agree with it; I code C# for a living and often find myself edging towards a functional style for certain problems. However, I think you're a bit strident; not all refactoring is simply a progression towards using map, foldr, and filter; similarly, I think you're overly harsh on Java and C#. C# at least is moving in interesting directions - LINQ is providing something very similar to (if more verbose than) Haskell's list comprehensions, and also now supports lambdas and a form of type inference. Whilst it's never going to be as much fun writing C# as it is to write Haskell or Ruby (which are my preferred languages outside the office, along with Ocaml), it's encouraging that such a mainstream language is starting to "get it". 

I hold my hand up and concede that my phrasing didn't really communicate any of this. Sorry. I'm just getting used to blogging and realise I need to be careful about how people interpret my writing.</description>
		<content:encoded><![CDATA[<p>&#8220;I bring this to your attention so as not to continue the proliferation of mythology and mislead potentially innocent bystanders into a similar state of delusion.&#8221;</p>
<p>The phrase &#8220;everyone knows that&#8221; was intended to be slightly tongue-in-cheek, which I had hoped would be picked up by being unnecessarily sweeping and all-encompassing. Generally speaking I think it&#8217;s a good thing, but I also think Steve Yegge hit the nail on the head when he said that refactoring had become the <a href="http://steve.yegge.googlepages.com/transformation" rel="nofollow">goal rather than the cure</a>.</p>
<p>I read your <a href="http://blog.tmorris.net/refunctoring/" rel="nofollow">Refunctoring</a> article and largely agree with it; I code C# for a living and often find myself edging towards a functional style for certain problems. However, I think you&#8217;re a bit strident; not all refactoring is simply a progression towards using map, foldr, and filter; similarly, I think you&#8217;re overly harsh on Java and C#. C# at least is moving in interesting directions - LINQ is providing something very similar to (if more verbose than) Haskell&#8217;s list comprehensions, and also now supports lambdas and a form of type inference. Whilst it&#8217;s never going to be as much fun writing C# as it is to write Haskell or Ruby (which are my preferred languages outside the office, along with Ocaml), it&#8217;s encouraging that such a mainstream language is starting to &#8220;get it&#8221;. </p>
<p>I hold my hand up and concede that my phrasing didn&#8217;t really communicate any of this. Sorry. I&#8217;m just getting used to blogging and realise I need to be careful about how people interpret my writing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JS</title>
		<link>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-3</link>
		<dc:creator>JS</dc:creator>
		<pubDate>Fri, 14 Dec 2007 07:05:41 +0000</pubDate>
		<guid>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-3</guid>
		<description>After all, 'terrible code' is by definition any software code you yourself didn't write.  Right?</description>
		<content:encoded><![CDATA[<p>After all, &#8216;terrible code&#8217; is by definition any software code you yourself didn&#8217;t write.  Right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Morris</title>
		<link>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-2</link>
		<dc:creator>Tony Morris</dc:creator>
		<pubDate>Thu, 13 Dec 2007 22:42:13 +0000</pubDate>
		<guid>http://basildoncoder.com/blog/2007/12/13/legacy-code-refactoring-and-ownership/#comment-2</guid>
		<description>&#62; Refactoring is good. Everyone knows that.

This is called an argumentum ad populum logical fallacy. Logical fallacies are very prolific in hyperbolic material such that which purports refactoring as anything but a perversion of science.

There exists one person who doesn't "know that Refactoring is good" and actively refutes the truth value of this statement (it is so false that the inverse is true). I wrote an article titled Refunctoring quite some time ago; I'll happily support my position with evidence and reason upon request.

I bring this to your attention so as not to continue the proliferation of mythology and mislead potentially innocent bystanders into a similar state of delusion.</description>
		<content:encoded><![CDATA[<p>&gt; Refactoring is good. Everyone knows that.</p>
<p>This is called an argumentum ad populum logical fallacy. Logical fallacies are very prolific in hyperbolic material such that which purports refactoring as anything but a perversion of science.</p>
<p>There exists one person who doesn&#8217;t &#8220;know that Refactoring is good&#8221; and actively refutes the truth value of this statement (it is so false that the inverse is true). I wrote an article titled Refunctoring quite some time ago; I&#8217;ll happily support my position with evidence and reason upon request.</p>
<p>I bring this to your attention so as not to continue the proliferation of mythology and mislead potentially innocent bystanders into a similar state of delusion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.268 seconds -->
