<?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: Sign Your Work: Individuality</title>
	<atom:link href="http://www.programmersparadox.com/2008/01/29/sign-your-work-individuality/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.programmersparadox.com/2008/01/29/sign-your-work-individuality/</link>
	<description>Is anything I write real?</description>
	<lastBuildDate>Wed, 21 Apr 2010 13:23:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Mark</title>
		<link>http://www.programmersparadox.com/2008/01/29/sign-your-work-individuality/comment-page-1/#comment-60</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 30 Jan 2008 03:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2008/01/29/sign-your-work-individuality/#comment-60</guid>
		<description>Do most programmers actually sign their work?  I tend to think that most actually don&#039;t.  Certainly there are those that do.  

Also, consider the Agile context, where the code is supposed to be its own comments.  When it is done correctly, the code can be self explanatory, so there isn&#039;t much need for many comments - but I still think programmers should sign their work in this case.

And ultimately, it comes down to having pride in your work and taking ownership.  That&#039;s really what signing it is all about.  Not just about dry comments explaining what is going on.</description>
		<content:encoded><![CDATA[<p>Do most programmers actually sign their work?  I tend to think that most actually don&#8217;t.  Certainly there are those that do.  </p>
<p>Also, consider the Agile context, where the code is supposed to be its own comments.  When it is done correctly, the code can be self explanatory, so there isn&#8217;t much need for many comments &#8211; but I still think programmers should sign their work in this case.</p>
<p>And ultimately, it comes down to having pride in your work and taking ownership.  That&#8217;s really what signing it is all about.  Not just about dry comments explaining what is going on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noah</title>
		<link>http://www.programmersparadox.com/2008/01/29/sign-your-work-individuality/comment-page-1/#comment-59</link>
		<dc:creator>noah</dc:creator>
		<pubDate>Wed, 30 Jan 2008 02:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.programmersparadox.com/2008/01/29/sign-your-work-individuality/#comment-59</guid>
		<description>Umm... they are expected to sign their work.  Just because you don&#039;t comment your code correctly doesn&#039;t mean you&#039;re not supposed to.</description>
		<content:encoded><![CDATA[<p>Umm&#8230; they are expected to sign their work.  Just because you don&#8217;t comment your code correctly doesn&#8217;t mean you&#8217;re not supposed to.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
