<?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: Refactoring the Monster</title>
	<link>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster</link>
	<description>Stories of a Self-published, Entrepreneurial Fiction Author (and Software Guy)</description>
	<pubDate>Wed, 07 Jan 2009 08:13:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: J. Timothy King</title>
		<link>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7470</link>
		<dc:creator>J. Timothy King</dc:creator>
		<pubDate>Wed, 05 Jul 2006 00:15:30 +0000</pubDate>
		<guid>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7470</guid>
		<description>Thanks for the kind words, Gavin, Retrospector, and Michael. I'm still learning, but it's a good feeling.

Michael, that's an epiphany I wish for all software development organizations. Pair programming increases effectiveness and thus reduces cost.

I did get to pair at times with each of my teammates, though I didn't mention it in the story. I wish I had more opportunity to do so. The primary goal of this pairing was to share knowledge about the code. That's an easy sell. I don't know to sell continuous pairing to the organization, much less my team-lead, who once even refused to let me pair with him... But that's another story.

-TimK</description>
		<content:encoded><![CDATA[<p>Thanks for the kind words, Gavin, Retrospector, and Michael. I&#8217;m still learning, but it&#8217;s a good feeling.</p>
<p>Michael, that&#8217;s an epiphany I wish for all software development organizations. Pair programming increases effectiveness and thus reduces cost.</p>
<p>I did get to pair at times with each of my teammates, though I didn&#8217;t mention it in the story. I wish I had more opportunity to do so. The primary goal of this pairing was to share knowledge about the code. That&#8217;s an easy sell. I don&#8217;t know to sell continuous pairing to the organization, much less my team-lead, who once even refused to let me pair with him&#8230; But that&#8217;s another story.</p>
<p>-TimK</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Feathers</title>
		<link>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7468</link>
		<dc:creator>Michael Feathers</dc:creator>
		<pubDate>Tue, 04 Jul 2006 10:40:27 +0000</pubDate>
		<guid>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7468</guid>
		<description>Great story!  One word of warning, though.  Reducing costs isn't as easy as it seems.  It isn't just a matter of getting the lower cost person on the things that look mechanical.  The way to really reduce costs is get the guy with the most understanding to pair with everyone else.  It doesn't matter if he's the most expensive guy.  I think that the thing that raises costs more than anything else in software is lack of understanding.  And, this seems to be true for all sorts of understanding.. low level understanding of techniques, API.. the big picture, etc.

I love the egg metaphor, btw.</description>
		<content:encoded><![CDATA[<p>Great story!  One word of warning, though.  Reducing costs isn&#8217;t as easy as it seems.  It isn&#8217;t just a matter of getting the lower cost person on the things that look mechanical.  The way to really reduce costs is get the guy with the most understanding to pair with everyone else.  It doesn&#8217;t matter if he&#8217;s the most expensive guy.  I think that the thing that raises costs more than anything else in software is lack of understanding.  And, this seems to be true for all sorts of understanding.. low level understanding of techniques, API.. the big picture, etc.</p>
<p>I love the egg metaphor, btw.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Retrospector</title>
		<link>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7451</link>
		<dc:creator>Retrospector</dc:creator>
		<pubDate>Mon, 03 Jul 2006 18:19:27 +0000</pubDate>
		<guid>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7451</guid>
		<description>Ah, the thrill of driving progress at the lead position.  I remember a very similar engagement when converting old VBA apps to a Java environment with a small team.  I think being a good IT manager really does require some sort of insight from experiences that had both the successes and the failures.</description>
		<content:encoded><![CDATA[<p>Ah, the thrill of driving progress at the lead position.  I remember a very similar engagement when converting old VBA apps to a Java environment with a small team.  I think being a good IT manager really does require some sort of insight from experiences that had both the successes and the failures.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gavin</title>
		<link>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7444</link>
		<dc:creator>Gavin</dc:creator>
		<pubDate>Mon, 03 Jul 2006 15:56:29 +0000</pubDate>
		<guid>http://blog.jtimothyking.com/2006/07/01/refactoring-the-monster#comment-7444</guid>
		<description>Hey. Nice story. I'm glad it turned out positive and not another bitch session/horror story like most I read (think dailywtf.com). Good for you!

Gav</description>
		<content:encoded><![CDATA[<p>Hey. Nice story. I&#8217;m glad it turned out positive and not another bitch session/horror story like most I read (think dailywtf.com). Good for you!</p>
<p>Gav</p>
]]></content:encoded>
	</item>
</channel>
</rss>
