<?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: Reusable code vs. re-editable code</title>
	<atom:link href="http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/</link>
	<description>The blog of John D. Cook</description>
	<lastBuildDate>Sat, 11 Feb 2012 22:42:11 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Why programmers are not paid in proportion to their productivity &#8212; The Endeavour</title>
		<link>http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/comment-page-1/#comment-129252</link>
		<dc:creator>Why programmers are not paid in proportion to their productivity &#8212; The Endeavour</dc:creator>
		<pubDate>Tue, 10 Jan 2012 14:24:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/#comment-129252</guid>
		<description>[...] doesn&#8217;t actually want what they&#8217;re asking for. They may know where to find reusable or re-editable code that solves their problem. They may cheat. But just when they are being their most productive, [...]</description>
		<content:encoded><![CDATA[<p>[...] doesn&#8217;t actually want what they&#8217;re asking for. They may know where to find reusable or re-editable code that solves their problem. They may cheat. But just when they are being their most productive, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Opening black boxes &#8212; The Endeavour</title>
		<link>http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/comment-page-1/#comment-106474</link>
		<dc:creator>Opening black boxes &#8212; The Endeavour</dc:creator>
		<pubDate>Wed, 05 Oct 2011 13:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/#comment-106474</guid>
		<description>[...] Reusable code versus re-editable code    ? X [...]</description>
		<content:encoded><![CDATA[<p>[...] Reusable code versus re-editable code    ? X [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier</title>
		<link>http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/comment-page-1/#comment-78108</link>
		<dc:creator>Olivier</dc:creator>
		<pubDate>Wed, 27 Apr 2011 21:37:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/#comment-78108</guid>
		<description>On the other hand, standard library code is reusable code, not re-editable code. But it&#039;s so good that it&#039;s ok to reuse it even if you don&#039;t edit it. Reusing printf is fine.</description>
		<content:encoded><![CDATA[<p>On the other hand, standard library code is reusable code, not re-editable code. But it&#8217;s so good that it&#8217;s ok to reuse it even if you don&#8217;t edit it. Reusing printf is fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/comment-page-1/#comment-29519</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Thu, 24 Dec 2009 06:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/#comment-29519</guid>
		<description>&quot;Good code is easy to change.
All code will change until it is no longer easy to change.
All code becomes bad code.&quot;

--Unknown

Basic lessons in entropy, applied to programming...</description>
		<content:encoded><![CDATA[<p>&#8220;Good code is easy to change.<br />
All code will change until it is no longer easy to change.<br />
All code becomes bad code.&#8221;</p>
<p>&#8211;Unknown</p>
<p>Basic lessons in entropy, applied to programming&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Doolin</title>
		<link>http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/comment-page-1/#comment-9017</link>
		<dc:creator>Dave Doolin</dc:creator>
		<pubDate>Tue, 04 Nov 2008 04:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/2008/05/03/reusable-code-vs-re-editable-code/#comment-9017</guid>
		<description>I can see both sides of this coin, and offer a more personal take on the subject: re-usable code is code that *I* can re-edit!

The art of developing interfaces to libraries to promote &quot;black box&quot; re-usability of code is something not covered (to my knowledge) in TAOCP, nor should it be.</description>
		<content:encoded><![CDATA[<p>I can see both sides of this coin, and offer a more personal take on the subject: re-usable code is code that *I* can re-edit!</p>
<p>The art of developing interfaces to libraries to promote &#8220;black box&#8221; re-usability of code is something not covered (to my knowledge) in TAOCP, nor should it be.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.305 seconds -->

