Building a Startup on Clojure
Ah clojure. It&#x27;s all fun and games until five years down the line, you&#x27;ve had 100% dev churn, and you have a 100kloc codebase that nobody understands, full of functions that don&#x27;t give the slightest hint of the shape of the data they&#x27;re processing (it&#x27;s all lists!) yet down the bottom of the callstack there&#x27;s some function that&#x27;ll explode if the map doesn&#x27;t have whatever magical key it expects.<p>If you&#x27;re really lucky, someone will have thrown in a bunch of &#x27;specs&#x27; that make a bunch of assertions about the data, put them on the API entry points, and then scattered some slightly different specs with slightly more restrictive assertions on various &#x27;internal APIs&#x27;, resulting in random explosions in production!<p>And the joy of working with an esoteric language is that it attracts esoteric developers, who often get frustrated by the requirements of being a software engineer in a large company (i.e. everything that&#x27;s not writing code), which leads to the aforementioned 100% dev churn (after a lot of shouting).