<story><title>Alan Kay has agreed to do an AMA today</title><text>This request originated via recent discussions on HN, and the forming of HARC! at YC Research. I&amp;#x27;ll be around for most of the day today (though the early evening).</text></story><parent_chain><item><author>di</author><text>Hi Alan,&lt;p&gt;In &amp;quot;The Power of the Context&amp;quot; (2004) you wrote:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  ...In programming there is a wide-spread 1st order
  theory that one shouldn’t build one’s own tools,
  languages, and especially operating systems. This is
  true—an incredible amount of time and energy has gone
  down these ratholes. On the 2nd hand, if you can build
  your own tools, languages and operating systems, then
  you absolutely should because the leverage that can be
  obtained (and often the time not wasted in trying to
  fix other people’s not quite right tools) can be
  incredible.
&lt;/code&gt;&lt;/pre&gt;
I love this quote because it justifies a DIY attitude of experimentation and reverse engineering, etc., that generally I think we could use more of.&lt;p&gt;However, more often than not, I find the sentiment paralyzing. There&amp;#x27;s so much that one could &lt;i&gt;probably&lt;/i&gt; learn to build themselves, but as things become more and more complex, one has to be able to make a rational tradeoff between spending the time and energy in the rathole, or not. I can&amp;#x27;t spend all day rebuilding everything I can simply because I &lt;i&gt;can&lt;/i&gt;.&lt;p&gt;My question is: how does one decide when to DIY, and when to use what&amp;#x27;s already been built?</text></item></parent_chain><comment><author>alankay</author><text>This is a tough question. (And always has been in a sense, because every era has had projects where the tool building has sunk the project into a black hole.)&lt;p&gt;It really helped at Parc to work with real geniuses like Chuck Thacker and Dan Ingalls (and quite a few more). There is a very thin boundary between making the 2nd order work vs getting wiped out by the effort.&lt;p&gt;Another perspective on this is to think about &amp;quot;not getting caught by dependencies&amp;quot; -- what if there were really good &lt;i&gt;independent module systems&lt;/i&gt; -- perhaps aided by hardware -- that allowed both worlds to work together (so one doesn&amp;#x27;t get buried under &amp;quot;useful patches&amp;quot;, etc.)&lt;p&gt;One of my favorite things to watch at Parc was how well Dan Ingalls was able to bootstrap a new system out of an old one by really using what objects are good for, and especially where the new system was even much better at facilitating the next bootstrap.&lt;p&gt;I&amp;#x27;m not a big Unix fan -- it was too late on the scene for the level of ideas that it had -- but if you take the cultural history it came from, there were several things they tried to do that were admirable -- including really having a tiny kernel and using Unix processes for all systems building (this was a very useful version of &amp;quot;OOP&amp;quot; -- you just couldn&amp;#x27;t have small objects because of the way processes were implemented). It was quite sad to see how this pretty nice mix and match approach gradually decayed into huge loads and dependencies. Part of this was that the rather good idea of parsing non-command messages in each process -- we used this in the first Smalltalk at Parc -- became much too ad hoc because there was not a strong attempt to intertwine a real language around the message structures (this very same thing happened with http -- just think of what this could have been if anyone had been noticing ...)</text></comment>
<story><title>Alan Kay has agreed to do an AMA today</title><text>This request originated via recent discussions on HN, and the forming of HARC! at YC Research. I&amp;#x27;ll be around for most of the day today (though the early evening).</text></story><parent_chain><item><author>di</author><text>Hi Alan,&lt;p&gt;In &amp;quot;The Power of the Context&amp;quot; (2004) you wrote:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  ...In programming there is a wide-spread 1st order
  theory that one shouldn’t build one’s own tools,
  languages, and especially operating systems. This is
  true—an incredible amount of time and energy has gone
  down these ratholes. On the 2nd hand, if you can build
  your own tools, languages and operating systems, then
  you absolutely should because the leverage that can be
  obtained (and often the time not wasted in trying to
  fix other people’s not quite right tools) can be
  incredible.
&lt;/code&gt;&lt;/pre&gt;
I love this quote because it justifies a DIY attitude of experimentation and reverse engineering, etc., that generally I think we could use more of.&lt;p&gt;However, more often than not, I find the sentiment paralyzing. There&amp;#x27;s so much that one could &lt;i&gt;probably&lt;/i&gt; learn to build themselves, but as things become more and more complex, one has to be able to make a rational tradeoff between spending the time and energy in the rathole, or not. I can&amp;#x27;t spend all day rebuilding everything I can simply because I &lt;i&gt;can&lt;/i&gt;.&lt;p&gt;My question is: how does one decide when to DIY, and when to use what&amp;#x27;s already been built?</text></item></parent_chain><comment><author>stcredzero</author><text>Isn&amp;#x27;t the answer contained in the quote? Do a cost&amp;#x2F;benefit analysis of the &amp;quot;amount of time and energy&amp;quot; that would go &amp;quot;down these ratholes&amp;quot; versus the &amp;quot;the time not wasted in trying to fix other people’s not quite right tools.&amp;quot;</text></comment>