<?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: Real World Refactoring</title>
	<atom:link href="http://lostechies.com/joshuaflanagan/2009/06/29/real-world-refactoring/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/joshuaflanagan/2009/06/29/real-world-refactoring/</link>
	<description></description>
	<lastBuildDate>Thu, 14 Mar 2013 03:50:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Jason Meridth</title>
		<link>http://lostechies.com/joshuaflanagan/2009/06/29/real-world-refactoring/#comment-49</link>
		<dc:creator>Jason Meridth</dc:creator>
		<pubDate>Wed, 01 Jul 2009 04:34:36 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joshuaflanagan/archive/2009/06/28/real-world-refactoring.aspx#comment-49</guid>
		<description>Excellent write-up Josh. Showed this to a few friends having issues understanding OCP, DIP and ISP. This was perfect real world example.</description>
		<content:encoded><![CDATA[<p>Excellent write-up Josh. Showed this to a few friends having issues understanding OCP, DIP and ISP. This was perfect real world example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zbigg</title>
		<link>http://lostechies.com/joshuaflanagan/2009/06/29/real-world-refactoring/#comment-48</link>
		<dc:creator>zbigg</dc:creator>
		<pubDate>Mon, 29 Jun 2009 14:42:19 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joshuaflanagan/archive/2009/06/28/real-world-refactoring.aspx#comment-48</guid>
		<description>Agree with pulling up registration outside. But this introspection thing is one step too far:

1. Explicit declaration of parser list is great place for self documenting all comment parsing rules:

2. For first time reader it&#039;s very easy to find these rules at first look without browsing whole source tree. 

3. They create readable and trackable explicit dependency.

As long as program is quite monolithic one shouldn&#039;t put plugin interfaces everywhere. Plugin/extension points should be choosen carefully and not by making everything pluggable.
</description>
		<content:encoded><![CDATA[<p>Agree with pulling up registration outside. But this introspection thing is one step too far:</p>
<p>1. Explicit declaration of parser list is great place for self documenting all comment parsing rules:</p>
<p>2. For first time reader it&#8217;s very easy to find these rules at first look without browsing whole source tree. </p>
<p>3. They create readable and trackable explicit dependency.</p>
<p>As long as program is quite monolithic one shouldn&#8217;t put plugin interfaces everywhere. Plugin/extension points should be choosen carefully and not by making everything pluggable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Gregory</title>
		<link>http://lostechies.com/joshuaflanagan/2009/06/29/real-world-refactoring/#comment-47</link>
		<dc:creator>James Gregory</dc:creator>
		<pubDate>Mon, 29 Jun 2009 11:12:35 +0000</pubDate>
		<guid isPermaLink="false">/blogs/joshuaflanagan/archive/2009/06/28/real-world-refactoring.aspx#comment-47</guid>
		<description>Hey Josh,

Excellent refactoring, and a great writeup too. The pulling up of the responsibility to the bootstrapper makes the parser much more flexible too, as you can substitute the node parsers depending on configuration (or environment).

We need more examples like this. I&#039;ll gladly write some more highly coupled code if you&#039;ll write up how to fix it ;)

Thanks again for putting the work into Docu as well, it&#039;s much appreciated.</description>
		<content:encoded><![CDATA[<p>Hey Josh,</p>
<p>Excellent refactoring, and a great writeup too. The pulling up of the responsibility to the bootstrapper makes the parser much more flexible too, as you can substitute the node parsers depending on configuration (or environment).</p>
<p>We need more examples like this. I&#8217;ll gladly write some more highly coupled code if you&#8217;ll write up how to fix it ;)</p>
<p>Thanks again for putting the work into Docu as well, it&#8217;s much appreciated.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
