@agentultra For me, the goal is to be able to divide code up into functions with names that (hopefully) explain obviously what they're doing. So someone reading it would think "I don't need to dive into that, because it's clear what it's doing"

Imo writing your code as a big long procedural recipe just means you didn't make an effort to factor it nicely.

@agentultra I think it's because your types outline the problem you're solving, and it's hard to fully comprehend the problem before you write any code.

Which is why I think Haskell is so cool, because it's easy to update the types as you go. GHC will just tell you everything you need to fix.