I’ve spent a lot of my career around software, teams, systems, product questions, and the kinds of decisions that only become clear after you’ve lived with the tradeoffs for a while.
I’m interested in software as a technical craft, but also in the wider shape of the work: how decisions get made, how systems become more or less coherent over time, how teams regain traction when things drift, and how product and technical questions start to blur together in real environments.
A lot of what I write about comes from that overlap. Some posts start from architecture or platform concerns. Some start from leadership, execution, or uncertainty. Some come from the way new tools, especially AI tools, are changing the practical texture of software work. Most of them are really about judgment in one form or another.
I’m not especially interested in writing as performance. I like essays that begin with an honest question, stay close to reality, and make some attempt to say what is actually true. That usually means writing with less certainty than the internet prefers, but hopefully with more usefulness.
This site is a place to collect those thoughts in one spot. Sometimes that means longer essays. Sometimes it means smaller notes or observations that feel worth keeping.