dybr

So, nobody approved my "documenter" code; sent them a reminder; tomorrow I'll be pinging them on slack.

Meanwhile I was fixing that "version upgrade" project. cats librarty sucks, monad transformers suck, crazy Spanish programmers were building something like Sagrada, no taste, no harmony, just a tall pile of shit.

Eventually I made it work, but did not like the way the code looks, so asked Esteban and Sam to take a look and suggest any ideas to make it readabler.

Imagine, you might slap together an error Response (HTTP 400), with some custom message. Normally that's all you need, and you then send it.

But why t.f. the authors of HTTP4S want a "Kleisli"? that is, you have to provide a function that takes a request (in this specific case we ignore the request), and return an OptionT(Async[IO[Response])? So I spent some time wrapping my response into IO, Async, OptionT. They call it Kleisli. I bet it was either Travis or Daniel that slapped together this kind of nonsense.

Well, whatever.

And besides, the build script in that project had a bug, and that bug prefented running Scalafix/Scalacheck. I fixed the bug, then spent some time fixing the style.