I like it. It&#x27;s a keeper. Also the argument is a bit overstated.<p><i>&quot;...The moral of this story is that secondary and tertiary effects matter....Employers much prefer that workers be fungible, rather than maximally productive...[in regards to creating a larger framework] The reason why this doesn&#x27;t happen is because of the Lisp Curse. Large numbers of Lisp hackers would have to cooperate with each other...&quot;</i><p>So here&#x27;s what I see. I see a lot of frameworks and libraries composed by folks using other languages. Many of these, yes, are much more complete than one, totally-custom-made solution by some Lisp hacker. And yes, large numbers of people participate in creating and maintaining these larger frameworks and systems.<p>I also see large corporations <i>bleeding</i> cash because they wanted silo&#x27;ed, fungible programmers. Got seven architectural tiers, each with its own framework? Hell, you&#x27;re going to need seven extremely specialized programmers, kid. Time to get on the phone with the recruiter.<p>So they purchase these specialists. All the buzzwords match. The specialists sit down at the magic frameworks, the ones all the cool kids over the last two years have decided to support. Life is good. For about ten minutes. Then something is required that&#x27;s not in the frameworks. Or the framework is broken under this one particular edge case.<p>Suddenly we need somebody who&#x27;s general purpose again. Except -- and this is especially nice -- that&#x27;s not the guy we hired. So seven layers of experts sit struggling with seven oddball issues. Googling Stack Overflow. Hacking the crap out of things. Making a total mess.<p>And at the end of the day, if we&#x27;re lucky, something ships. Something with little problems here and there that requires seven different areas of expertise to figure out. Plan on maintenance being fun.<p>The next day version 2.0 of the framework on layer 5 ships. Now if you want maintenance programmers, for layer 5 they have to know both version 1.0 and 2.0<p>More complexity continues. It&#x27;s fun for everybody.<p>Compare this to the guy who uses a standard language, decades-old libraries, hacks out a partial solution (but good enough to ship) in a few days and then moves on to something else. Now tell me that the framework guys have a better technology development model. I ain&#x27;t believing it.<p>I&#x27;m not saying become a lone wolf and never work with folks. I&#x27;m saying that &quot;working with folks&quot; can completely kill any kind of value you&#x27;re trying to create. Do it wisely.