<?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: A Class Isn&#8217;t Always a Noun</title>
	<atom:link href="http://www.agileatwork.com/a-class-isnt-always-a-noun/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileatwork.com/a-class-isnt-always-a-noun/</link>
	<description>by Michael Valenty</description>
	<lastBuildDate>Thu, 05 Jan 2012 07:24:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Valenty</title>
		<link>http://www.agileatwork.com/a-class-isnt-always-a-noun/comment-page-1/#comment-248</link>
		<dc:creator>Michael Valenty</dc:creator>
		<pubDate>Tue, 08 Dec 2009 00:03:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileatwork.com/?p=230#comment-248</guid>
		<description>Sure it&#039;s possible not to violate the rule, but the point I&#039;m making is that it&#039;s not necessary or valuable to follow it dogmatically. Each link in the chain of responsibility implements IFilter&lt;T&gt;, they could all have the suffix &#039;Filter&#039; and I could prefix member variables with &#039;m_&#039; too. I think the pomp and circumstance is just noise and forces the reader to do unnecessary mental mapping.</description>
		<content:encoded><![CDATA[<p>Sure it&#8217;s possible not to violate the rule, but the point I&#8217;m making is that it&#8217;s not necessary or valuable to follow it dogmatically. Each link in the chain of responsibility implements IFilter&lt;T&gt;, they could all have the suffix &#8216;Filter&#8217; and I could prefix member variables with &#8216;m_&#8217; too. I think the pomp and circumstance is just noise and forces the reader to do unnecessary mental mapping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Asaph</title>
		<link>http://www.agileatwork.com/a-class-isnt-always-a-noun/comment-page-1/#comment-247</link>
		<dc:creator>Asaph</dc:creator>
		<pubDate>Mon, 07 Dec 2009 19:02:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileatwork.com/?p=230#comment-247</guid>
		<description>I believe it would still be possible to stick to the &quot;all-classes-must-be-nouns&quot; rule without compromising your fluent interface. Your code would still read like a DSL. Consider the following:

&lt;pre class=&quot;prettyprint&quot;&gt;
&lt;code&gt;
    private void SyncListing()
    {
        new LocatorChain&lt;Yextlisting&gt;(locator)
            .AddNew&lt;DiscontinuedListingReverter&gt;()
            .AddNew&lt;LinkedBusinessRefresher&gt;()
            .AddNew&lt;ExistingBusinessLinker&gt;()
            .AddNew&lt;NewBusinessLinker&gt;()
            .Process(listing);
    }
&lt;/code&gt;
&lt;/pre&gt;
Is that really less readable?</description>
		<content:encoded><![CDATA[<p>I believe it would still be possible to stick to the &#8220;all-classes-must-be-nouns&#8221; rule without compromising your fluent interface. Your code would still read like a DSL. Consider the following:</p>
<pre class="prettyprint">
<code>
    private void SyncListing()
    {
        new LocatorChain&lt;Yextlisting&gt;(locator)
            .AddNew&lt;DiscontinuedListingReverter&gt;()
            .AddNew&lt;LinkedBusinessRefresher&gt;()
            .AddNew&lt;ExistingBusinessLinker&gt;()
            .AddNew&lt;NewBusinessLinker&gt;()
            .Process(listing);
    }
</code>
</pre>
<p>Is that really less readable?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

