Haskell Mini-Patterns Handbook

This is great. I can say I&#x27;ve used and encountered literally all of these techniques many times in every Haskell codebase I&#x27;ve joined and built.<p>The concise cost&#x2F;benefit analysis very helpful.

This is a gem. I have been looking for this kind of clear and to the point explanations of common Haskell patterns for a long time.

These patterns are not only applicable to Haskell but FP and programming in general. I am using them with a Typescript codebase.

This is a great post, I’ve seen a lot of those patterns before and it’s nice to have them in one place! One criticism I have though is I’m not sure about the advantage of phantom types, it seems like boilerplate to me. I feel like generalized algebraic data types are a strictly better pattern to follow to solve the issue of restricting type variable bindings to specific types.

Thanks for this. The tasks are a nice touch!

Anyone else have trouble with the page on firefox? I get a giant &quot;kowainik&quot; written on the forefront of the page, and I don&#x27;t know how to close it.

I do not write Haskell, but this is a neat site.

This is a beautiful start but much more content. Send PRs to kowainik.

The most deadly sin with Haskell is introducing unnecessary redundant abstractions to impress other people.<p>Imagine aircraft engineers will do that.<p>Up to (but not including) NonEmpty lists everything was fine.

The whole &quot;this code is problematic because... &quot; section on Boolean blindness reminds me of the worst caricatures of left-wing narratives of oppression based on PhD-level Critical Theory.<p>Look, a lot of the other patterns are interesting but I really think that if you are getting into criticising code because it has &quot;Boolean blindness&quot; you are probably getting a bit lost in navel gazing. Do you really have nothing better to do?