The vocabulary we have around burn out is insufficient. It's often framed as too much work (which is definitely one factor), but I see it also stem from misalignment in terms of strategy or values, lack of recognition, and/or sense of belonging.

Game Developers: I'm gonna make this machine render beautiful vibrant landscapes 60 times per second. Web Developers: This newspaper article needs at least 7 seconds to show up and will boil your computer alive if you try to scroll too fast.

Imagining the joy I’d feel during dev and code review if Dict wasn’t a thing, but Pudding was: data Pudding :: Constraint -> * where Proof :: c => Pudding c

The curse of engineering is that everything is obvious after the fact. The fact that it took you n weeks and a half dozen design docs to figure it out is instantly forgotten.

The Hidden Dangers of Haskell's Ratio Type fpcomplete.com/blog/hidden-da…

Uncurled - everything I know and learned about running and maintaining Open Source projects for three decades daniel.haxx.se/blog/2022/04/3… un.curl.dev

Wrote some Groovy in Jenkins for the first time today and found some known bug with closure-based loops only processing the first list item. SO advised sidestepping this bug with a counter-based for loop, so that stuff got put in a “Groovy’s got hands” commit.

Announcing monad-logger-aeson: Structured logging in Haskell for cheap jship.github.io/posts/2022-05-…

New #haskell & #compiler blogpost: "How to lower an IR"! luctielen.com/posts/how-to-l… The hardest thing with compiler blogposts is to avoid having to write a full compiler for each article. 😅

I am looking for a new Haskell job! * used Haskell since 2006 * professionally since 2017 * lead architect of a code base with half a million lines of Haskell code since 2019 GitHub github.com/gelisam YouTube haskellcat.com Blog gelisam.com

do you ever think about how the industry-standard way of configuring C projects is to generate a script that tests the host C compiler against hundreds of dummy programs, reporting whether or not they throw errors

tfw trying to read pg source docs on a phone, especially when the sidebar collapse doesn’t work in my browser

Isn't this beautiful?

ki 1.0.0, a structured concurrency library for Haskell, hot out of the oven! hackage: hackage.haskell.org/package/ki github: github.com/awkward-squad/… reddit announcement: reddit.com/r/haskell/comm… discourse announcement: discourse.haskell.org/t/ki-1-0-0-a-l…

I keep abusing evil evil implicit parameters as a better/faster ReaderT IO pattern, but that raises the question of how to handle backtracking on error. Since (?foo :: a) gets reified as IP "foo" a, we can write some somewhat cursed combinators for this. gist.github.com/ekmett/04595b4…

Haskell performance pro tip for (most) concurrent programs: don't do anything in the main thread. Just forkIO the real main and wait until it's done.

throwback to some truly sicko code i wrote a while ago (this is pure haskell)

🚰🥤 I present you with a pragmatic guide for avoiding space leaks in #Haskell programs. After using Haskell in anger for the last 7 years, I developed P̵T̵S̵D̵ best practices for reducing unnecessary memory usage. No 👏 more 👏 space 👏 leaks 👏 kodimensional.dev/space-leak

Gave a #haskell talk last Friday on revisiting MTL and ReaderT: youtu.be/vhqa_n1n0dI