<?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: Imbeciles in the Wild</title>
	<atom:link href="http://www.jeremyprivett.com/blog/archives/imbeciles-in-the-wild/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jeremyprivett.com/blog/archives/imbeciles-in-the-wild/</link>
	<description>Programming and Life</description>
	<lastBuildDate>Tue, 29 Sep 2009 22:01:20 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dutch</title>
		<link>http://www.jeremyprivett.com/blog/archives/imbeciles-in-the-wild/comment-page-1/#comment-118013</link>
		<dc:creator>Dutch</dc:creator>
		<pubDate>Sun, 27 Jul 2008 11:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/blog/?p=259#comment-118013</guid>
		<description>There&#039;s a couple of interesting problems with code comments. The first is the additional overall bytes size of a file. In large projects this becomes expesive overhead. Granted, with modern systems this means a lot less than it used to. However, when you are releasing to a mixed audience of users and user systems it becomes something to take into account again.

Then again, there are wonderful things which have come about as a result of old needs to minimize the overall byte size. As an OO Developer I would expect to see some healthy UML out of you Jeremy. This would have mitigated a few headaches I had when supporting your work post your leaving the building. At that point in time, some clearer comments would have sufficed well too.

The problem I&#039;ve seen many developers have in commenting their code boils down to a simple thing: the next poor bastage who has to work on it just may be less skilled than you. If you seek to leave a place better than you found it leave a clear instruction manual where you sat.

Of course, code that is still in place and common use as half of the staple product offering over a year after you were released for supposedly being short of the desired skill level is good approach too.</description>
		<content:encoded><![CDATA[<p>There&#8217;s a couple of interesting problems with code comments. The first is the additional overall bytes size of a file. In large projects this becomes expesive overhead. Granted, with modern systems this means a lot less than it used to. However, when you are releasing to a mixed audience of users and user systems it becomes something to take into account again.</p>
<p>Then again, there are wonderful things which have come about as a result of old needs to minimize the overall byte size. As an OO Developer I would expect to see some healthy UML out of you Jeremy. This would have mitigated a few headaches I had when supporting your work post your leaving the building. At that point in time, some clearer comments would have sufficed well too.</p>
<p>The problem I&#8217;ve seen many developers have in commenting their code boils down to a simple thing: the next poor bastage who has to work on it just may be less skilled than you. If you seek to leave a place better than you found it leave a clear instruction manual where you sat.</p>
<p>Of course, code that is still in place and common use as half of the staple product offering over a year after you were released for supposedly being short of the desired skill level is good approach too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://www.jeremyprivett.com/blog/archives/imbeciles-in-the-wild/comment-page-1/#comment-114925</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Sat, 12 Jul 2008 00:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/blog/?p=259#comment-114925</guid>
		<description>It could make sense if most of the developer&#039;s comments were like &quot;// set $x to 4&quot;, which could happen if they&#039;re in the middle of an intro CS course where they tell you to comment everything. I mainly just comment the purpose of classes/functions/properties, and any complex code blocks that might confuse others (or me) down the road.</description>
		<content:encoded><![CDATA[<p>It could make sense if most of the developer&#8217;s comments were like &#8220;// set $x to 4&#8243;, which could happen if they&#8217;re in the middle of an intro CS course where they tell you to comment everything. I mainly just comment the purpose of classes/functions/properties, and any complex code blocks that might confuse others (or me) down the road.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Babcock</title>
		<link>http://www.jeremyprivett.com/blog/archives/imbeciles-in-the-wild/comment-page-1/#comment-114909</link>
		<dc:creator>Ben Babcock</dc:creator>
		<pubDate>Fri, 11 Jul 2008 21:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.jeremyprivett.com/blog/?p=259#comment-114909</guid>
		<description>Heck, I&#039;ve had so many problems over the years that could&#039;ve been solved if _I_ had commented my stuff properly. :P</description>
		<content:encoded><![CDATA[<p>Heck, I&#8217;ve had so many problems over the years that could&#8217;ve been solved if _I_ had commented my stuff properly. <img src='http://www.jeremyprivett.com/blog/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
