<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: A comment on comments</title>
	<link>http://www.xaprb.com/blog/2005/09/28/a-comment-on-comments/</link>
	<description>Stay curious!</description>
	<pubDate>Fri, 08 Aug 2008 18:51:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Nathaniel Schwartz</title>
		<link>http://www.xaprb.com/blog/2005/09/28/a-comment-on-comments/#comment-16</link>
		<author>Nathaniel Schwartz</author>
		<pubDate>Sun, 04 Dec 2005 20:21:02 +0000</pubDate>
		<guid>http://www.xaprb.com/blog/2005/09/28/a-comment-on-comments/#comment-16</guid>
		<description>&lt;p&gt;I think I know what you are talking about. I know some people here at VCU who used 1300 lines of code to do what I did in about 300 lines; a more experienced (in my case Java) programmer could probably have weeded it down to 150. I am of the opinion that less code is more elegant and easier to understand most of the time. Sometimes it helps to clarify if you step things out a little bit more. As for comments, I guess it's hard to comment if you don't know what your code is doing!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I think I know what you are talking about. I know some people here at VCU who used 1300 lines of code to do what I did in about 300 lines; a more experienced (in my case Java) programmer could probably have weeded it down to 150. I am of the opinion that less code is more elegant and easier to understand most of the time. Sometimes it helps to clarify if you step things out a little bit more. As for comments, I guess it&#8217;s hard to comment if you don&#8217;t know what your code is doing!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
