<?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: 5 Reasons I Love To Delete Code</title>
	<atom:link href="http://www.summa-tech.com/blog/2009/08/05/5-reasons-i-love-to-delete-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.summa-tech.com/blog/2009/08/05/5-reasons-i-love-to-delete-code/</link>
	<description>Summa Blog</description>
	<pubDate>Wed, 08 Feb 2012 05:04:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: raveman</title>
		<link>http://www.summa-tech.com/blog/2009/08/05/5-reasons-i-love-to-delete-code/comment-page-1/#comment-1392</link>
		<dc:creator>raveman</dc:creator>
		<pubDate>Fri, 07 Aug 2009 13:21:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.summa-tech.com/blog/?p=1129#comment-1392</guid>
		<description>dont u think that its better to move code somewhere than to delete it? for example lets say that ur company doesnt need pdf reports and will never use it again. Then year later they want pdf reports back, why go on search in source control when u can have it in special folder in your project? folder named something like abandonware. plus if you delete something u wont be able to find it year later (if project is not maintainence only)</description>
		<content:encoded><![CDATA[<p>dont u think that its better to move code somewhere than to delete it? for example lets say that ur company doesnt need pdf reports and will never use it again. Then year later they want pdf reports back, why go on search in source control when u can have it in special folder in your project? folder named something like abandonware. plus if you delete something u wont be able to find it year later (if project is not maintainence only)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Changsu</title>
		<link>http://www.summa-tech.com/blog/2009/08/05/5-reasons-i-love-to-delete-code/comment-page-1/#comment-1390</link>
		<dc:creator>Changsu</dc:creator>
		<pubDate>Fri, 07 Aug 2009 01:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.summa-tech.com/blog/?p=1129#comment-1390</guid>
		<description>Good stuff. Same thing advocated by Uncle Bob in his "Clean Code"</description>
		<content:encoded><![CDATA[<p>Good stuff. Same thing advocated by Uncle Bob in his &#8220;Clean Code&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: K</title>
		<link>http://www.summa-tech.com/blog/2009/08/05/5-reasons-i-love-to-delete-code/comment-page-1/#comment-1389</link>
		<dc:creator>K</dc:creator>
		<pubDate>Thu, 06 Aug 2009 23:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.summa-tech.com/blog/?p=1129#comment-1389</guid>
		<description>Another advantage is that the deleted code can be in a place that is called frequently. This will also speed up the program</description>
		<content:encoded><![CDATA[<p>Another advantage is that the deleted code can be in a place that is called frequently. This will also speed up the program</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Holloway</title>
		<link>http://www.summa-tech.com/blog/2009/08/05/5-reasons-i-love-to-delete-code/comment-page-1/#comment-1384</link>
		<dc:creator>Matt Holloway</dc:creator>
		<pubDate>Wed, 05 Aug 2009 19:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.summa-tech.com/blog/?p=1129#comment-1384</guid>
		<description>Great stuff Jim.  While talking about a new person, here's another point... the new person may also be given a task to fix a bug, but may put the fix in the wrong method (the one that should have been deleted), and then struggle to find out why it isn't working.  Many of the old methods may have names that are similar to the new methods (or appropriate methods)... deleteCustomer() versus customerDelete() or something.  

Just the time spent isolating the proper method (even if we are only talking about a few lines of code) reduces developer productivity. Remember the 'Joel on Software' article that talks about distractions to developers?  If a developer (new) needs to interrupt another developer to discuss the methods, then two developers have now been taken out of 'the zone', costing each 30 minutes... multiply that by the number of methods that should have been deleted, and you'd have a costly mess over a few lines of worthless code.</description>
		<content:encoded><![CDATA[<p>Great stuff Jim.  While talking about a new person, here&#8217;s another point&#8230; the new person may also be given a task to fix a bug, but may put the fix in the wrong method (the one that should have been deleted), and then struggle to find out why it isn&#8217;t working.  Many of the old methods may have names that are similar to the new methods (or appropriate methods)&#8230; deleteCustomer() versus customerDelete() or something.  </p>
<p>Just the time spent isolating the proper method (even if we are only talking about a few lines of code) reduces developer productivity. Remember the &#8216;Joel on Software&#8217; article that talks about distractions to developers?  If a developer (new) needs to interrupt another developer to discuss the methods, then two developers have now been taken out of &#8216;the zone&#8217;, costing each 30 minutes&#8230; multiply that by the number of methods that should have been deleted, and you&#8217;d have a costly mess over a few lines of worthless code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

