Picking up #Haskell is not a matter of "If" but of "When".
When your head overflows with UML diagrams instead of expressive yet concise types?
When your systems belch runtime exceptions like a Weezing?
When shared mutable state prevents you from understanding what the hell is happening?
Some people hear “ #Haskell 's type system eliminates entire classes of bugs” and think “Cool, no tests needed”.
But what you should hear is “Cool, we can focus on more interesting tests”.
Golden tests, property tests, doctests…
https://wiki.haskell.org/index.php?title=How_to_write_a_Haskell_program#Testing
Turned my #zurihac2025 talk on #competitiveprogramming in #Haskell into an expanded blog post:
https://byorgey.github.io/blog/posts/2025/06/10/comprog-hs-intro.html