<?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: No, your code is not so great that it doesn&#8217;t need comments</title>
	<atom:link href="http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/</link>
	<description>Rants and opinion interspersed with awe-inspiring tales of heoric software engineering endeavours.</description>
	<pubDate>Tue, 06 Jan 2009 21:42:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2579</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 20 Aug 2008 14:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2579</guid>
		<description>The gt; is supposed to be a greater than sign.  It's messed up by Wordpress.  I'll see if I can fix it.</description>
		<content:encoded><![CDATA[<p>The gt; is supposed to be a greater than sign.  It&#8217;s messed up by Wordpress.  I&#8217;ll see if I can fix it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jabongga</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2526</link>
		<dc:creator>Jabongga</dc:creator>
		<pubDate>Mon, 18 Aug 2008 18:35:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2526</guid>
		<description>hi man i know this is a C# but what is the &#38;gt? i keep on getting an error in while clause.

I'm a beginner btw thanks</description>
		<content:encoded><![CDATA[<p>hi man i know this is a C# but what is the &amp;gt? i keep on getting an error in while clause.</p>
<p>I&#8217;m a beginner btw thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chat Marchet News Digest &#187; No, your code is not so great that it doesn’t need comments</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2350</link>
		<dc:creator>Chat Marchet News Digest &#187; No, your code is not so great that it doesn’t need comments</dc:creator>
		<pubDate>Wed, 13 Aug 2008 04:10:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2350</guid>
		<description>[...] Read the story  This entry was posted on Wednesday, August 13th, 2008 at 1:03 am and is filed under le Chat Marchet. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. [...]</description>
		<content:encoded><![CDATA[<p>[...] Read the story  This entry was posted on Wednesday, August 13th, 2008 at 1:03 am and is filed under le Chat Marchet. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2337</link>
		<dc:creator>Gareth</dc:creator>
		<pubDate>Tue, 12 Aug 2008 11:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2337</guid>
		<description>The why in comments needs to be used judiciously in my opinion. If you are creating object methods and, as you should as an OOP programmer, be considering re-use, the why is not necessary as this will change with each different implementation and can be seen as a limiting factor. Rather include the why into the method call than as a part of the actual method itself. That way you wont be editing (or forgetting to edit) the comment with each new implementation.</description>
		<content:encoded><![CDATA[<p>The why in comments needs to be used judiciously in my opinion. If you are creating object methods and, as you should as an OOP programmer, be considering re-use, the why is not necessary as this will change with each different implementation and can be seen as a limiting factor. Rather include the why into the method call than as a part of the actual method itself. That way you wont be editing (or forgetting to edit) the comment with each new implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Another Pissing Contest</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2255</link>
		<dc:creator>Another Pissing Contest</dc:creator>
		<pubDate>Fri, 08 Aug 2008 22:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2255</guid>
		<description>I am just SO sick of the whole "I am a better programmer/coder/developer/etc than you because I think this way" mentality, that I could seriously puke on each and every one of you.

We all work our asses off all day doing something we love, and what do we get for it? We get some guy who, just because he has a web site which now a blog, thinking he is better/smarter/whatever and his senseless/brainless sheep followers who bitch because we don't think like he does.

Just because you do something one way, doesn't mean it is the ONLY way to do it. GET OVER YOURSELF and do something constructive.</description>
		<content:encoded><![CDATA[<p>I am just SO sick of the whole &#8220;I am a better programmer/coder/developer/etc than you because I think this way&#8221; mentality, that I could seriously puke on each and every one of you.</p>
<p>We all work our asses off all day doing something we love, and what do we get for it? We get some guy who, just because he has a web site which now a blog, thinking he is better/smarter/whatever and his senseless/brainless sheep followers who bitch because we don&#8217;t think like he does.</p>
<p>Just because you do something one way, doesn&#8217;t mean it is the ONLY way to do it. GET OVER YOURSELF and do something constructive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Creaking Under The Weight Of Links &#124; Programmer's Log</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2232</link>
		<dc:creator>Creaking Under The Weight Of Links &#124; Programmer's Log</dc:creator>
		<pubDate>Thu, 07 Aug 2008 21:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2232</guid>
		<description>[...] No, your code is not so great that it doesn’t need comments I like rants that tell you to comment your code. Just because you can understand the intention it does not mean that others will interpret the information in the same fashion. [...]</description>
		<content:encoded><![CDATA[<p>[...] No, your code is not so great that it doesn’t need comments I like rants that tell you to comment your code. Just because you can understand the intention it does not mean that others will interpret the information in the same fashion. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How bad comments are born in your code &#124; Little Tutorials</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2185</link>
		<dc:creator>How bad comments are born in your code &#124; Little Tutorials</dc:creator>
		<pubDate>Tue, 05 Aug 2008 18:30:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2185</guid>
		<description>[...] recent posts Dan Dyer and Jeff Attwood took somehow different positions regarding what good comments are and if we need [...]</description>
		<content:encoded><![CDATA[<p>[...] recent posts Dan Dyer and Jeff Attwood took somehow different positions regarding what good comments are and if we need [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2184</link>
		<dc:creator>James</dc:creator>
		<pubDate>Tue, 05 Aug 2008 18:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2184</guid>
		<description>Wolter:

"The top comments were done in javadoc style. It’s more of a habit for me and not strictly necessary because, as you have said, we know from the names what it does, and “n” is pretty obvious as well."

- Point taken and I can see where you're coming from.

"There is absolutely NO need to learn all about square root algorithms to fix errors in this code."

"I have absolutely NO idea what square root algorithms there are out there, nor do I care, nor should I care."

"I would be a simple user of the library..."

- I completely agree. There's really no need for us (and I also consider myself an expert since I've been in the software development business for 10 years and have built countless, both crappy and exquisite, software solutions for varied companies in many different fields) to learn anything about square roots. I have no time for that either. You shouldn't care, and I shouldn't care either. But that dude that ends up maintaining exactly that piece of code we don't even want to see ever, does care. Comments are not gonna be enough to instruct him on the proper method used in the code, unless you bloat the code with a copy paste from wikipedia between multiline comments. Nevertheless, a search for "approximateSquareRoot" will get the person to this blog and he'll have all the info he'll ever need about naming conventions and where to look for square roots explanations. If he searches for "approximate Square Root" he'll get a webpage with this title "How to calculate a square root without a calculator" (and an explanation to rule over all other explanations on this particular issue); and a wikipedia page that explains the newtons method in a way simple enough to grasp what he needs to do.

"In fact, if I were to come across such a situation, I’d probably just throw the library away and go with something else."

- So would I...

"I work in the real world. I have a job to do, and I don’t have time to fuck around."

- So do I. And so does the guy that does need to maintain that code. For you and me, it means using another library. For the other dude, it means either reading this humongous comment on the code (and most programmers are not good at explaining things.... oh the irony), or googling the procedure name and actually finding everything he needs to know in a smaller more organized package.</description>
		<content:encoded><![CDATA[<p>Wolter:</p>
<p>&#8220;The top comments were done in javadoc style. It’s more of a habit for me and not strictly necessary because, as you have said, we know from the names what it does, and “n” is pretty obvious as well.&#8221;</p>
<p>- Point taken and I can see where you&#8217;re coming from.</p>
<p>&#8220;There is absolutely NO need to learn all about square root algorithms to fix errors in this code.&#8221;</p>
<p>&#8220;I have absolutely NO idea what square root algorithms there are out there, nor do I care, nor should I care.&#8221;</p>
<p>&#8220;I would be a simple user of the library&#8230;&#8221;</p>
<p>- I completely agree. There&#8217;s really no need for us (and I also consider myself an expert since I&#8217;ve been in the software development business for 10 years and have built countless, both crappy and exquisite, software solutions for varied companies in many different fields) to learn anything about square roots. I have no time for that either. You shouldn&#8217;t care, and I shouldn&#8217;t care either. But that dude that ends up maintaining exactly that piece of code we don&#8217;t even want to see ever, does care. Comments are not gonna be enough to instruct him on the proper method used in the code, unless you bloat the code with a copy paste from wikipedia between multiline comments. Nevertheless, a search for &#8220;approximateSquareRoot&#8221; will get the person to this blog and he&#8217;ll have all the info he&#8217;ll ever need about naming conventions and where to look for square roots explanations. If he searches for &#8220;approximate Square Root&#8221; he&#8217;ll get a webpage with this title &#8220;How to calculate a square root without a calculator&#8221; (and an explanation to rule over all other explanations on this particular issue); and a wikipedia page that explains the newtons method in a way simple enough to grasp what he needs to do.</p>
<p>&#8220;In fact, if I were to come across such a situation, I’d probably just throw the library away and go with something else.&#8221;</p>
<p>- So would I&#8230;</p>
<p>&#8220;I work in the real world. I have a job to do, and I don’t have time to fuck around.&#8221;</p>
<p>- So do I. And so does the guy that does need to maintain that code. For you and me, it means using another library. For the other dude, it means either reading this humongous comment on the code (and most programmers are not good at explaining things&#8230;. oh the irony), or googling the procedure name and actually finding everything he needs to know in a smaller more organized package.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Adventures in Software &#187; Revisiting the Comments Debate: The Self-Documenting Code Contest</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2182</link>
		<dc:creator>New Adventures in Software &#187; Revisiting the Comments Debate: The Self-Documenting Code Contest</dc:creator>
		<pubDate>Tue, 05 Aug 2008 16:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2182</guid>
		<description>[...] No, your code is not so great that it doesn&#8217;t need comments  [...]</description>
		<content:encoded><![CDATA[<p>[...] No, your code is not so great that it doesn&#8217;t need comments  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: proc</title>
		<link>http://blog.uncommons.org/2008/07/25/no-your-code-is-not-so-great-that-it-doesnt-need-comments/comment-page-2/#comment-2152</link>
		<dc:creator>proc</dc:creator>
		<pubDate>Mon, 04 Aug 2008 07:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.uncommons.org/?p=100#comment-2152</guid>
		<description>on the flip side of things....
why commenting can be bad

http://w.holeso.me/2008/08/the-dark-side-of-code-commenting/</description>
		<content:encoded><![CDATA[<p>on the flip side of things&#8230;.<br />
why commenting can be bad</p>
<p><a href="http://w.holeso.me/2008/08/the-dark-side-of-code-commenting/" rel="nofollow">http://w.holeso.me/2008/08/the-dark-side-of-code-commenting/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

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