I will try to remember him for his far too relatable Dilbert comics about corporate office life, and not his, uhm, later work.
One of my favorite strips was Dilbert in the 90s only being given a 286 PC for 3D rendering work, with the boss saying "besides, how often will you do 3D rendering in your career?"
My bad. I had been reading about how there's a frustration in the community that allistic people refuse to explain why such statements are wrong, and instead just repeat "you know what you did!" to people who genuinely don't.
I tried to be the one who didn't do that, but missed the mark. I'd delete it if I could.
It feels like we're back in 1900 when anyone's clever idea (and implementation) can give huge performance improvements, such as Ford's assembly line and Taylor's scientific management of optimizing shovel sizes for coal.
I'm surprised there are no UTF-8 specific decode instructions yet, the way ARM has "FJCVTZS - Floating-point Javascript Convert to Signed fixed-point, rounding toward Zero"
I worked on this project for a week during the FB team matching process.
I had previous Haskell experience, but what struck me was how irrelevant that was.
To their immense credit, they had managed to use Haskell to write an entirely entreprise focused, "boring" business rule backend serving millions of QPS, and people who were not Haskell fans could easily use its sensible DSL to accomplish their goals.
Way too many Haskell projects are about Haskell itself, so this was really fascinating to see.
My school dentist always botched the anesthesia, and afterwards I had to grind my teeth for three days to make them fit together again.
I never told anyone because adults kept saying dentistry hurts so I assumed it was normal. I didn't realize how fucked up this was until I went to college and experienced a competent dentist for the first time.
Tbh if you've never done either, I can absolutely see why getting on and riding a machine 1000x your size is a bigger deal than seeing various animals from a distance.