> But are they more productive, get shit that we care about done [...] I think there's a balance to be struck between "getting shit done" and "write something

> But are they more productive, get shit that we care about done [...] I think there's a balance to be struck between "getting shit done" and "write something that will be maintainable in the future". It might be true that (some?) Haskellers overdo it, but I've definitely seen enough of the "let's just get shit done" people who create messes that are completely unmaintainable and full of bugs after just a year or two. And IMHO, the software industry is in a really sorry state, considering how bug-riddled most software is, how most software projects fail or are considerably above budget, etc. [1] I've seen quite a number of failed projects in the companies I've been so far, a number of them involving quite a lot of resources. I've seen companies trying to rewrite hopeless messes and failing at it, grinding everything to a halt, because the code base is full of implicit assumptions that nobody bothered to properly specify anywhere. I've read about Shopify spending a whole year to upgrade to a newer version of Ruby on Rails.[2] Probably the industry doesn't yet know how best to find this balance but I don't think that the Haskellers are solely to blame for this. [1]: https://danluu.com/everything-is-broken/ https://danluu.com/everything-is-broken/ [2]: https://shopify.engineering/upgrading-shopify-to-rails-5-0 https://shopify.engineering/upgrading-shopify-to-rails-5-0