A new notebook

This is the first post on a blog I just spun up. Calling it a “blog” is probably too generous. It’s really a working notebook. I wanted a public place to write down what I learn, and I wanted the writing to force me to actually understand the things I’m poking at.

Why I’m writing this

I’ve spent years shipping platform code for Kubernetes, service mesh, and distributed systems at planet scale on products such as Azure Kubernetes Service (AKS). Good work, but the ground is shifting, and with the advent of AI and LLMs, new problems are emerging. A lot of what I learned building substrate for one workload class turns out to be relevant to the next one, but not all of it, and the parts that aren’t are what I want to write about.

I can read papers about that. I can watch talks. What I can’t do is get the intuition for those problems without building the thing and writing about the building. So this exists as the “writing about the building” half.

What’s next

Whenever I learn something interesting, I’ll write it up here. I don’t have any set plans for what the next post will be, but the idea is just to keep learning and to keep writing.