I found useful as a primer on CRDT in general
High level views on how owning your own data works across multiple devices.
An examination of the idea of owning and controlling the data produced and used by the software that you use, rather than giving it to cloud services.
Suggestions for common pages you might like to see on a personal website.
Lots of neat little features to make a blog really shine. Some of them are obvious, like RSS feeds. Others are more appropriate to blogs more honed in on longer, focused pieces. Some of them are just QOL.
It's more accurate to call it a bunch of software engineering advice, as most of it is about engineering practices, particularly on large, team-based projects.
An analysis of complex systems, how they can (and do) fail, and how to manage their failure and their operation.
Advice on being braver as a programmer. This is actually good advice for anything where you can't really do any damage be screwing up,
A call to action for (re-)building a web designed for humans, not for capitalism
A look at how (I assume some parts of) Google does design documents for their projects
High level summary of the concepts discussed in Database Internals by Alex Petrov and Designing Data-Intensive Applications by Martin Kleppmann
Tips on communicating progress via updates to people who are interested or need to know
Incomplete walkthrough on building your own database
Come for the pun in the title, stay for the look at how database systems structure data on disks.
Dead hang exercise, using body weight to improve upper body strength
How this one family improved some land through light touch techniques to rejuvenate the soil.
Some tips on communication. Basically, be concise, get to the point, create structure.
Basically "Choose Boring Technology" (cited and linked in the first couple of paragraphs) and then expanded with "and these are the choices I made"
Walkthrough of setting up a Kubernetes cluster on a set of Orange Pi 0s