<?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: The Literacy of Programs</title>
	<atom:link href="http://www.nagarro.com/blog/the-literacy-of-programs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nagarro.com/blog/the-literacy-of-programs/</link>
	<description>Nagarro blog: software development, design, architecture and usability</description>
	<lastBuildDate>Fri, 30 Jul 2010 13:51:47 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Amit Jain</title>
		<link>http://www.nagarro.com/blog/the-literacy-of-programs/comment-page-1/#comment-144</link>
		<dc:creator>Amit Jain</dc:creator>
		<pubDate>Sat, 15 Dec 2007 22:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.nagarro.net/kayser/the-literacy-of-programs/#comment-144</guid>
		<description>Vaibhav,
Most of the time the useless comments are produced when code commenting is done after the coding is complete. A developer does this just to satify himself that he is following good coding practices.

It is a good practice to write comments at the same time (or earlier than) you write your code.

Commenting while you code forces you to make sure your logic &quot;sounds right&quot;. Plus, your comments are going to be more accurate when the understanding of what&#039;s going on behind-the-scenes is fresh in your mind.</description>
		<content:encoded><![CDATA[<p>Vaibhav,<br />
Most of the time the useless comments are produced when code commenting is done after the coding is complete. A developer does this just to satify himself that he is following good coding practices.</p>
<p>It is a good practice to write comments at the same time (or earlier than) you write your code.</p>
<p>Commenting while you code forces you to make sure your logic &#8220;sounds right&#8221;. Plus, your comments are going to be more accurate when the understanding of what&#8217;s going on behind-the-scenes is fresh in your mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Kayser</title>
		<link>http://www.nagarro.com/blog/the-literacy-of-programs/comment-page-1/#comment-143</link>
		<dc:creator>Bill Kayser</dc:creator>
		<pubDate>Tue, 02 Oct 2007 05:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.nagarro.net/kayser/the-literacy-of-programs/#comment-143</guid>
		<description>Hi Vaibhav.  Yes, that&#039;s me during my visit to Delhi a couple of years ago.  Manas Fuloria gave me the full tour including the campus of IIT, which I&#039;d heard so much about.

I agree with your point about useless comments.  Yesterday I came across a class called &quot;LinkAdapter&quot; which stated plainly in it&#039;s class comment &quot;The methods for the LinkAdapter class.&quot;  It&#039;s hard to imagine a less helpful class comment, and this was from a very competent developer!  I think people are sometimes conflicted between leaving useless comments and leaving nothing at all.

My opinion is that when thinking about what should be commented a developer should think about their &quot;audience&quot;.  Imagine what someone would be looking for if they ever happened upon this class, method or variable.  Use your experience as a programmer looking at other people&#039;s code to determine what information you would want to know.  Don&#039;t focus on guidelines and the compulsion to leave comments.  In the spirit of literate programming, focus on the people who will be reading them.

I talk more about this in the next post.</description>
		<content:encoded><![CDATA[<p>Hi Vaibhav.  Yes, that&#8217;s me during my visit to Delhi a couple of years ago.  Manas Fuloria gave me the full tour including the campus of IIT, which I&#8217;d heard so much about.</p>
<p>I agree with your point about useless comments.  Yesterday I came across a class called &#8220;LinkAdapter&#8221; which stated plainly in it&#8217;s class comment &#8220;The methods for the LinkAdapter class.&#8221;  It&#8217;s hard to imagine a less helpful class comment, and this was from a very competent developer!  I think people are sometimes conflicted between leaving useless comments and leaving nothing at all.</p>
<p>My opinion is that when thinking about what should be commented a developer should think about their &#8220;audience&#8221;.  Imagine what someone would be looking for if they ever happened upon this class, method or variable.  Use your experience as a programmer looking at other people&#8217;s code to determine what information you would want to know.  Don&#8217;t focus on guidelines and the compulsion to leave comments.  In the spirit of literate programming, focus on the people who will be reading them.</p>
<p>I talk more about this in the next post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vaibhav</title>
		<link>http://www.nagarro.com/blog/the-literacy-of-programs/comment-page-1/#comment-142</link>
		<dc:creator>Vaibhav</dc:creator>
		<pubDate>Mon, 01 Oct 2007 13:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.nagarro.net/kayser/the-literacy-of-programs/#comment-142</guid>
		<description>Hmm... just noticed by Ajay, the picture has the IIT Delhi Convocation hall in the background... Interesting... what&#039;s the story behind that?</description>
		<content:encoded><![CDATA[<p>Hmm&#8230; just noticed by Ajay, the picture has the IIT Delhi Convocation hall in the background&#8230; Interesting&#8230; what&#8217;s the story behind that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vaibhav</title>
		<link>http://www.nagarro.com/blog/the-literacy-of-programs/comment-page-1/#comment-141</link>
		<dc:creator>Vaibhav</dc:creator>
		<pubDate>Sun, 30 Sep 2007 11:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.nagarro.net/kayser/the-literacy-of-programs/#comment-141</guid>
		<description>Hello Bill,

While I can&#039;t help but agree that code should be written so that it can be &#039;read&#039;; one problem that I often come across (and not just in Nagarro, but in a lot of open source code that I get to read) is that there are often times useless comments.

These comments actually break the flow of a piece of code you are trying to read. And the main reason for these comments is that programmers are pummeled again and again by people telling them that comments are critical.

Like you very rightly said, a program is a piece of literature; does one need to be a good writer to judge correctly which comments are needed and which are simply in the way? Or is this something that can be taught/learned?

Cheers.</description>
		<content:encoded><![CDATA[<p>Hello Bill,</p>
<p>While I can&#8217;t help but agree that code should be written so that it can be &#8216;read&#8217;; one problem that I often come across (and not just in Nagarro, but in a lot of open source code that I get to read) is that there are often times useless comments.</p>
<p>These comments actually break the flow of a piece of code you are trying to read. And the main reason for these comments is that programmers are pummeled again and again by people telling them that comments are critical.</p>
<p>Like you very rightly said, a program is a piece of literature; does one need to be a good writer to judge correctly which comments are needed and which are simply in the way? Or is this something that can be taught/learned?</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
