<?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: Replacing Commented Code with Delegated Code</title> <atom:link href="http://ocpsoft.com/java/replacing-commented-code-with-delegated-code/feed/" rel="self" type="application/rss+xml" /><link>http://ocpsoft.com/java/replacing-commented-code-with-delegated-code/</link> <description>&#34;Simple Software&#34;</description> <lastBuildDate>Wed, 10 Mar 2010 15:23:38 +0000</lastBuildDate> <generator>http://wordpress.org/?v=2.9.2</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: Cathy</title><link>http://ocpsoft.com/java/replacing-commented-code-with-delegated-code/comment-page-1/#comment-88</link> <dc:creator>Cathy</dc:creator> <pubDate>Tue, 28 Oct 2008 15:57:56 +0000</pubDate> <guid
isPermaLink="false">http://ocpsoft.com/?p=6#comment-88</guid> <description>This is great info to know.</description> <content:encoded><![CDATA[<p>This is great info to know.</p> ]]></content:encoded> </item> <item><title>By: Sara</title><link>http://ocpsoft.com/java/replacing-commented-code-with-delegated-code/comment-page-1/#comment-10</link> <dc:creator>Sara</dc:creator> <pubDate>Mon, 04 Aug 2008 14:15:53 +0000</pubDate> <guid
isPermaLink="false">http://ocpsoft.com/?p=6#comment-10</guid> <description>lincolnthree - my new theology is &quot;don&#039;t comment unless it&#039;s weird&quot; unless it&#039;s something that is unconventional such as &quot;we had to do this this way because of the payment table being wonky&quot; or something of the sort commenting is only a crutch for non intuitive code.I try to make my variable/method names and code structure so obvious that a non-developer could look at it and tell you what it does.Once you have reached that point coding is zen.</description> <content:encoded><![CDATA[<p>lincolnthree &#8211; my new theology is &#8220;don&#8217;t comment unless it&#8217;s weird&#8221; unless it&#8217;s something that is unconventional such as &#8220;we had to do this this way because of the payment table being wonky&#8221; or something of the sort commenting is only a crutch for non intuitive code.</p><p>I try to make my variable/method names and code structure so obvious that a non-developer could look at it and tell you what it does.Once you have reached that point coding is zen.</p> ]]></content:encoded> </item> <item><title>By: Andreas</title><link>http://ocpsoft.com/java/replacing-commented-code-with-delegated-code/comment-page-1/#comment-9</link> <dc:creator>Andreas</dc:creator> <pubDate>Mon, 04 Aug 2008 10:03:23 +0000</pubDate> <guid
isPermaLink="false">http://ocpsoft.com/?p=6#comment-9</guid> <description>IMHO comments are more important for bugfixing than for reusability. In your comments you write down in your own words what your method is supposed to do. As a reviewer I can read the comment, understand the method and if I found a mismatch I found a bug.
So I clearly vote to do both. Commenting and writing easy to review code.</description> <content:encoded><![CDATA[<p>IMHO comments are more important for bugfixing than for reusability. In your comments you write down in your own words what your method is supposed to do. As a reviewer I can read the comment, understand the method and if I found a mismatch I found a bug.<br
/> So I clearly vote to do both. Commenting and writing easy to review code.</p> ]]></content:encoded> </item> <item><title>By: ranjan</title><link>http://ocpsoft.com/java/replacing-commented-code-with-delegated-code/comment-page-1/#comment-8</link> <dc:creator>ranjan</dc:creator> <pubDate>Mon, 04 Aug 2008 08:46:53 +0000</pubDate> <guid
isPermaLink="false">http://ocpsoft.com/?p=6#comment-8</guid> <description>i agree, if you need to write a comment to your code, its a smell. delegation and class/method names are the best way, and the moment you name a class right, which means you know what the job of the class is, you have reached a good object oriented design.</description> <content:encoded><![CDATA[<p>i agree, if you need to write a comment to your code, its a smell. delegation and class/method names are the best way, and the moment you name a class right, which means you know what the job of the class is, you have reached a good object oriented design.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: apache2-blow.brewers.dreamhost.com @ 2010-03-13 13:59:19 by W3 Total Cache -->