<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: the wrong duplication</title>
	<atom:link href="http://silkandspinach.net/2006/11/05/the-wrong-duplication/feed/" rel="self" type="application/rss+xml" />
	<link>http://silkandspinach.net/2006/11/05/the-wrong-duplication/</link>
	<description>development, by example</description>
	<lastBuildDate>Tue, 07 Feb 2012 05:40:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Kevin</title>
		<link>http://silkandspinach.net/2006/11/05/the-wrong-duplication/#comment-217</link>
		<dc:creator><![CDATA[Kevin]]></dc:creator>
		<pubDate>Tue, 07 Nov 2006 21:58:14 +0000</pubDate>
		<guid isPermaLink="false">http://silkandspinach.wordpress.com/2006/11/05/the-wrong-duplication/#comment-217</guid>
		<description><![CDATA[Hugh,  Now you raise the point, it does seem that the Pragmatics have been a little tautologous!  i take &#039;authoritative&#039; to mean the same as &#039;single&#039; in their statement.  As for &#039;unambiguous&#039;, I have no idea what they meant...

(BTW, comments do seem to accept simple HTML tags, so I&#039;ve re-instated your blockquote...)
]]></description>
		<content:encoded><![CDATA[<p>Hugh,  Now you raise the point, it does seem that the Pragmatics have been a little tautologous!  i take &#8216;authoritative&#8217; to mean the same as &#8216;single&#8217; in their statement.  As for &#8216;unambiguous&#8217;, I have no idea what they meant&#8230;</p>
<p>(BTW, comments do seem to accept simple HTML tags, so I&#8217;ve re-instated your blockquote&#8230;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nico Mommaerts</title>
		<link>http://silkandspinach.net/2006/11/05/the-wrong-duplication/#comment-216</link>
		<dc:creator><![CDATA[Nico Mommaerts]]></dc:creator>
		<pubDate>Mon, 06 Nov 2006 13:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://silkandspinach.wordpress.com/2006/11/05/the-wrong-duplication/#comment-216</guid>
		<description><![CDATA[I never thought about it that way... a very interesting observation!]]></description>
		<content:encoded><![CDATA[<p>I never thought about it that way&#8230; a very interesting observation!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hgs</title>
		<link>http://silkandspinach.net/2006/11/05/the-wrong-duplication/#comment-215</link>
		<dc:creator><![CDATA[hgs]]></dc:creator>
		<pubDate>Mon, 06 Nov 2006 11:41:54 +0000</pubDate>
		<guid isPermaLink="false">http://silkandspinach.wordpress.com/2006/11/05/the-wrong-duplication/#comment-215</guid>
		<description><![CDATA[That fits within the remit of the Pragmatic Programmers&#039;:
&lt;blockquote&gt;DRY---Don&#039;t Repeat Yourself:  Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.&lt;/blockquote&gt;

and usefully takes the idea to &quot;the next level&quot;. But this has made me think: how do we test for the other aspects of this?  How do we ensure the representation is unambiguous, and that it is authoritative?  Do there exist code fragments that exhibit these properties that can be shown to be refactored to avoid them?  All the examples of DRY I have seen have focussed on SINGLE....

All the whitespace I&#039;ve added to this comment to blockquote that citation has been collapsed, losing paragraph structure.  Hence all the &quot;\n\n&quot; stuff.  If this accepts any markup at all, then it would be useful to link to what is acceptable.]]></description>
		<content:encoded><![CDATA[<p>That fits within the remit of the Pragmatic Programmers&#8217;:</p>
<blockquote><p>DRY&#8212;Don&#8217;t Repeat Yourself:  Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.</p></blockquote>
<p>and usefully takes the idea to &#8220;the next level&#8221;. But this has made me think: how do we test for the other aspects of this?  How do we ensure the representation is unambiguous, and that it is authoritative?  Do there exist code fragments that exhibit these properties that can be shown to be refactored to avoid them?  All the examples of DRY I have seen have focussed on SINGLE&#8230;.</p>
<p>All the whitespace I&#8217;ve added to this comment to blockquote that citation has been collapsed, losing paragraph structure.  Hence all the &#8220;\n\n&#8221; stuff.  If this accepts any markup at all, then it would be useful to link to what is acceptable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Beacock</title>
		<link>http://silkandspinach.net/2006/11/05/the-wrong-duplication/#comment-214</link>
		<dc:creator><![CDATA[Andrew Beacock]]></dc:creator>
		<pubDate>Mon, 06 Nov 2006 08:58:36 +0000</pubDate>
		<guid isPermaLink="false">http://silkandspinach.wordpress.com/2006/11/05/the-wrong-duplication/#comment-214</guid>
		<description><![CDATA[Kevin,

I didn&#039;t realise until I read this post but I&#039;ve been needing something like this for a while. I always wondered why I didn&#039;t like long lists of static constants, always found them difficult to understand and prefered them inline (but not inline everywhere).

You have hit the nail on the head!  Good work!]]></description>
		<content:encoded><![CDATA[<p>Kevin,</p>
<p>I didn&#8217;t realise until I read this post but I&#8217;ve been needing something like this for a while. I always wondered why I didn&#8217;t like long lists of static constants, always found them difficult to understand and prefered them inline (but not inline everywhere).</p>
<p>You have hit the nail on the head!  Good work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

