Why I'm Keeping This Blog Small
A small place for notes on product-minded engineering, tradeoffs, and the details worth writing down.
I don't want this section of the site to turn into a second product that needs constant feeding.
There is already enough pressure on the internet to publish more, package ideas more cleanly, and turn every half-formed thought into content. That is not what I want this space to be.
I'm keeping it small on purpose.
Why small
Writing is useful to me when it helps me clarify something I actually believe: a product tradeoff, an implementation detail, a pattern I keep seeing, or a decision that looked minor at first and turned out to matter a lot.
That usually does not require a polished essay. Most of the time it just requires a short note and a clear point.
What will show up here
Most of what I write here will probably sit somewhere between product and engineering.
I care about that overlap more and more. The job boundaries are getting blurrier, especially in an AI-forward world where the leverage is often not just writing code, but knowing what to build, what to simplify, and what details are worth being stubborn about.
So this will be a place for notes on product-minded engineering, frontend and backend tradeoffs, and small implementation details that change the feel of a product more than people expect.
If a post feels too small to be an essay but too useful to forget, it probably belongs here.