<?xml version="1.0" encoding="UTF-8"?>
<wiki>
  <body>&lt;p&gt;If you write code with more code that&#8217;s fast now, you&#8217;re going to have a hit on your hands. And next year, you&#8217;re going to have a giant mess to maintain, and it&#8217;s going to slow you down adding features and fixing bugs, and someone&#8217;s going to come along and eat your lunch.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.wilshipley.com/blog/2005/02/free-programming-tips-are-worth-every.html&quot;&gt;Call me Fishmeal&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;At one point your code will deteriorate. You feel that the tools you used push you in a certain direction that is not feasible.&lt;/p&gt;
&lt;p&gt;But creating wholly new tools is hard, get your priorities straight. Sometimes it&amp;#8217;s wiser to&lt;/p&gt;
&lt;p&gt;&amp;#8230; fsck it, i want the perfect programming language. or at least a better one.+&lt;/p&gt;
&lt;h1&gt;instance_eval (pass method calls in a block to the instance)&lt;/h1&gt;
&lt;p&gt;http://hackety.org/2008/10/06/mixingOurWayOutOfInstanceEval.html&lt;/p&gt;
&lt;p&gt;eg&lt;/p&gt;
&lt;p&gt;&lt;code&gt;
&quot;bla&quot;.instance_eval do 
 to_s # bla
end&lt;/code&gt;&lt;/p&gt;</body>
  <created-at type="datetime">2008-04-16T15:55:28-07:00</created-at>
  <id type="integer">11382</id>
  <permalink>lessons-in-code-maintainability</permalink>
  <repository-id type="integer">6052</repository-id>
  <title>Lessons in Code Maintainability</title>
  <updated-at type="datetime">2009-07-04T03:53:21-07:00</updated-at>
  <user-id type="integer">3815</user-id>
</wiki>
