Reading Haskell: Teaching Haskell in Academia and Industry (panel)
Disclaimer: I've yet to write any significant body of Haskell.
I was struck by the notion that most people that work on Haskell spend a lot of time iterating to get a program that doesn't type check to one that does. It reminds me a lot of Python cycles spent getting a program that doesn't pass unit tests to one that does.
This to me sounds like feedback even earlier in the process of development. Sometimes, I don't stop to write the unit tests before the implementation because I've found a good implementation flow. And then I go through a crash-debug-fix cycle for a little bit. After it works, I realize it would've been faster to just write the test in the first place. Trade-offs, ya know?
I wonder how much I'd be able to lean on the compiler to support me writing my ideas down first?