<?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: Why I /do/ document and unit test</title>
	<atom:link href="http://www.kismith.co.uk/wordpress/index.php/2009/01/17/why-unit-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kismith.co.uk/wordpress/index.php/2009/01/17/why-unit-test/</link>
	<description>Incessant Ramblings</description>
	<lastBuildDate>Sun, 03 Apr 2011 14:07:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kev</title>
		<link>http://www.kismith.co.uk/wordpress/index.php/2009/01/17/why-unit-test/comment-page-1/#comment-10456</link>
		<dc:creator>Kev</dc:creator>
		<pubDate>Sat, 17 Jan 2009 20:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.kismith.co.uk/wordpress/?p=103#comment-10456</guid>
		<description>Sure - there are plenty of cases where it&#039;s worth commenting. In fact, I comment every method, parameter and return type for some projects - my point is that for the greatest number of cases, nothing more is required than the signature to know what a method does - for well factored code.

Definitely policy comments, like the Freevo one you describe, are invaluable.</description>
		<content:encoded><![CDATA[<p>Sure &#8211; there are plenty of cases where it&#8217;s worth commenting. In fact, I comment every method, parameter and return type for some projects &#8211; my point is that for the greatest number of cases, nothing more is required than the signature to know what a method does &#8211; for well factored code.</p>
<p>Definitely policy comments, like the Freevo one you describe, are invaluable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dirk Meyer</title>
		<link>http://www.kismith.co.uk/wordpress/index.php/2009/01/17/why-unit-test/comment-page-1/#comment-10455</link>
		<dc:creator>Dirk Meyer</dc:creator>
		<pubDate>Sat, 17 Jan 2009 20:00:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.kismith.co.uk/wordpress/?p=103#comment-10455</guid>
		<description>I agree that code should be self-documenting, but if I use a library from someone else, I don&#039;t want to read the code. Some nice doc string is everything I want. &quot;Can I provide a NULL pointer her?&quot; Yes, I can look in the code to figure it out, but why not say so in the doc? And about inline doc: two years ago I found a special &quot;if&quot; handling inside a function in Freevo (I guess I wrote myself). And I wondered: how can this happen? Since then I add a small comment &quot;handle special case because if the user did this two minutes ago, this can happen&quot;.</description>
		<content:encoded><![CDATA[<p>I agree that code should be self-documenting, but if I use a library from someone else, I don&#8217;t want to read the code. Some nice doc string is everything I want. &#8220;Can I provide a NULL pointer her?&#8221; Yes, I can look in the code to figure it out, but why not say so in the doc? And about inline doc: two years ago I found a special &#8220;if&#8221; handling inside a function in Freevo (I guess I wrote myself). And I wondered: how can this happen? Since then I add a small comment &#8220;handle special case because if the user did this two minutes ago, this can happen&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

