What this is
- meta
I use this site as a log. Not a finished write-up of work already done — notes from projects I am in the middle of, explanations I needed while building, and the detours that come with figuring things out.
The through-line is the work of building and understanding software: how it is designed, built, debugged, and operated. That usually means backend services in Go, distributed systems, cloud infrastructure, APIs, and the messy parts in between — debugging, performance, observability. AI-assisted development shows up when it is part of how the work actually happens. It is not the subject of every post.
I write from things I am building, investigating, or getting wrong. Some posts will follow a project. Some will be smaller: a tool, a dead end, a decision that did not hold up. I am not going to pretend everything worked on the first attempt.
The useful part, for me, is writing while the work is still moving. Experiments, opinions, and unfinished ideas belong here as much as things that shipped. What I can do is be clear about the context and the limits of each post.
If you want the short version: I explore, I build, and I write down what I learn as I go.