Gabriella Gonzalez on "Monad transformers are good, actually" @ZuriHac2023

I think a lot of people hate them. I gained a new appreciation and better understanding of them after watching Gabriella Gonzalez' talk "Monad transformers are good, actually" (which is an excellent presentation), but appreciation and understanding isn't the same as eagerness to and pleasure in using them extensively. (That is to say, the talk is good and worthwhile even if you don't end up liking them overall.) I had to google "Haskell handle pattern" and I haven't fully read the blog post yet, but I'm wondering if this is similar go Bluefin's approach to passing effect handlers(?) as explicit function parameters rather than implicitly via typeclass constraints. Tom Ellis' talk [Bluefin…

…you could refactor your glue code to RIO \~ Glue Vii. If the Effects bug bites you at a later stage you could refactor again to one of the sibling RIO++ effect systems for Glue Viii, Effectful or Bluefin depending on your tastes. OR ignore the above and stick with monad transformers but a least get a good explanation of how they work: \- [video \- https://github.com/mgrabmueller/TransformersStepByStep/blob/master/pdf/Transformers.pdf \- https://github.com/bookshelfdave/monad-transformers-step-by-step…

I did create a small scotty app to track my workouts and am refactoring bad looking parts trying to improve my Haskell. It feels like I could definetly make this less clunky code snippet. Perhaps with somethink like monad transformers? I saw a talk from gabriella at zurihac 23 here and this feels like a pretty similar pattern. Any advice or tips on how to fix the nested/repeated usage of `case ... of` with matching on Maybe or Either types are highly appreciated!