<story><title>In Defense of Copy and Paste</title><url>http://zacharyvoase.com/2013/02/08/copypasta/</url></story><parent_chain></parent_chain><comment><author>toomim</author><text>I love copy &amp;#38; paste!  I also defended it in this scholarly article: &lt;a href=&quot;http://harmonia.cs.berkeley.edu/papers/toomim-linked-editing.pdf&quot; rel=&quot;nofollow&quot;&gt;http://harmonia.cs.berkeley.edu/papers/toomim-linked-editing...&lt;/a&gt;
with a video: &lt;a href=&quot;http://youtu.be/1wo_7MTdWWI&quot; rel=&quot;nofollow&quot;&gt;http://youtu.be/1wo_7MTdWWI&lt;/a&gt;</text></comment>
<story><title>In Defense of Copy and Paste</title><url>http://zacharyvoase.com/2013/02/08/copypasta/</url></story><parent_chain></parent_chain><comment><author>bunderbunder</author><text>That example under the &lt;i&gt;When Tools Make It Worse&lt;/i&gt; section - uggghhhhh.  Why would anyone actually &lt;i&gt;do&lt;/i&gt; that?  That isn&apos;t DRY refactoring, that&apos;s cargo cult refactoring.&lt;p&gt;DRY is not, was never, and should never be about unnecessarily replacing clean, well-factored code with @$2!% shared mutable state. The goal is to normalize your code, not to micro-optimize for keystroke count. No.  Nonononononono. Just no.</text></comment>