There’s so much in this article where I look at it and I’m like, is this ai slop?

I’m beginning to really appreciate short articles with a few bullet point takeaways.

With respect to version control across systems, when you get into serious stuff where mistakes are measured in lives and/or three commas, there’s just a lot more simplicity in the design of those systems than most people think.

Really big systems often have very simple design principles at their core which are echoed through out the topology.

In secure code like the stuff signal uses, having a hash of the code that is attested by a network of servers and chained back to self-signed identities on the client is the only way to go.

Here’s the hash of the code that’s supposed to be running on my server, here’s the proof that I verified it with all of the hardware and software tools at my disposal from the server, and here’s that hash and attestation embedded into the app on your phone or laptop that’s connecting to my box.

If there’s an easier way to get some semblance of “my device is talking to the right code on the right box,” please enlighten me.