Announcing an operator lookup tool for OCaml! 🐫 🎉 https://t.co/U7etlhS63Y It takes an OCaml operator or syntax element and gives an explanation of its behaviour, usage examples and warnings about common misuses. Thanks to @JoshWComeau for the idea and design elements.

[private message on work slack] friend: hey buddy how do i <do thing>, i can't find it in your team's docs and i feel super dumb me: hey buddy! it doesn't exist. please re-ask this question in our public help channel so whoever is on-call can answer you. [public help channel]

I wrote about using confidential computing and reproducible builds to broker access to admin permissions at @monzo 🔒🏦 https://t.co/Io1SGcqvw9

Really lovely post by Patrick with lots of pointers to interesting open source work – he's been on quite a tour!

ah yes, increasing the speed of an OCaml program by up to 50% by predicting memory allocation patterns. The correctness is straightforward, but why is it faster ? When unrolled i get a 2x improvement over the naive loop.

I wrote a book about the Janet programming language:

There's a really glorious Terraform + Nix setup out there waiting for me if I could _just_ spend 5 years building it

Would love a Terraform provider for MacOS system preferences – bit fed up slowly re-creating the same config on each machine I ever use / reconciling drift manually.

Watch a billion dollar news company use my footage without licensing it

https://t.co/94RKK3156H

A sweet example of #offlinefirst application built using #Irmin and #OCaml. Backup your browser application data in Git on the server-side and use a 3-way merge strategy to reconcile any conflicts. Great work @dinakajoy !

Oh. Oh no.

Finally got around to fixing the initial dark mode flicker on my site 🎉 Only took me several years to get around to it... Dark mode + SSR always feels more complicated than it really should – props to @JoshWComeau for his excellent post on the subject.

Caching aside, I thought there would be more paranoid/risk-averse consumers of popular base images (distros) reproducing image hashes themselves (in multiple places / by multiple engineers), but looks like 99.99% just delegate trust to the vendor via signing & leave it at that.

Surprised that relatively few folks seem interested in having their Docker images be truly "reproducible" (in the byte-for-byte sense, not just a fuzzy notion of equivalent output). There seems to be plenty of ways to do it, but none of them seem to be used _that_ widely.

I'm getting ready to go back to the West Highlands next week so I thought I'd make a 'will it be raining when I'm in the West Highlands, and will I be able to see Ben Nevis this time, and also do I need my waterproofs?' map

DevX folks fighting the good fight, as usual :-)

Congratulations to @ztfasr for passing her PhD viva on “Secure Programming with Dispersed Compartments” today!!! Most exciting systems work on a full stack approach to using modern TEE hardware across the kernel/userspace/app layers. Keep an eye out for the final version…