In what is platform engineering?, I gave this definition:
Platform engineering, as a discipline, takes a coherent approach to improving an engineering organization's output in ways that the rest of the business can see and understand.
I've had some thoughts and discussions since then, though, and I think that definition needs revising. Specifically, I tried to be very clear in the last post that I didn't think platform engineering could/should be gatekept. Problem is, that previous definition has some scoping issues—mostly around vagueness—that could work against that goal.
Keep Reading (4 minutes) →I'm working on a book about writing local-first software. Instead of doing a survey of all the libraries available, I'm taking a first principles approach. That means doing a lot of explaining CRDTs, syncing, and the like, but I'm having a ton of fun with it so far.
As of mid-January 2025, I have the introduction and first chapter done, and I'm working on the implementation that will end up being built up throughout the book. This currently looks like a TUI that I am already using to see how the user experience is!
I hope to be at the place where beta readers can look at the book in early 2025!
This and 16 other projects →