Writing

I write to clarify what I think, especially when implementation makes the clean explanation stop working. Most pieces begin with something I built, a decision I’m unsure about, or a belief that changed.

I’d rather publish a few finished arguments than a list of things I intend to write.

Featured

Chat is not the workflow

4 min read

Conversation is useful while intent is forming. It becomes brittle when it also has to carry state, ownership, and consequences.

AI productsworkflowsproduct engineering

Why this site exists

2 min read

A place to explain the work, record how my thinking changes, and keep track of the rest of my life.

personalwriting

Questions I’m working through

These are open questions, not promised essays. If I reach an answer worth defending, it will become one.

When software is operated by a model, which assumptions that used to live in the user's head have to move into the product?
When is it better to make an action reversible than to require approval first?
What should a CRM treat as fact, interpretation, or memory?
How should a product distinguish a successful API call from a successful customer outcome?
Which parts of ambiguous work can be formalized, and which still require judgment?