Most engineering work disappears quickly if I do not write it down.

The important parts are usually not the final pull request or the finished feature. They are the small decisions made along the way: why one approach felt safer, what tradeoff was accepted, which assumption turned out to be wrong, and what should be easier next time.

I want this blog to work partly as a public work log. Not a polished archive of perfect conclusions, but a place to capture the texture of building software over time.

The goal is simple: write enough context that future me can recover the thinking.