Now · updated August 2026
What I’m working on right now
Teaching YarMail to stop asking twice
The pattern ledger works. What it lacks is a way to tell me why it changed its mind about a sender, which turns out to matter more than accuracy.
A shared question queue for the Saturday shop
Anyone in the house can clear a grocery question from their phone. The goal is that the shop never blocks on me being available.
Writing more, shipping slightly less
Two posts a month, cross-posted to LinkedIn. The mistakes are the useful part, so those go first.
Talking to people hiring builders
Open to product roles where defining and building are the same job. Get in touch.
What’s on my backlog?
Ten weeks bought several working apps. It also bought a list of things I started and deliberately said no or not-yet to: a data-access broker — one governed path in and out of the database, so an app or an AI session can ask a question without holding the keys; a scoped database connector that keeps an assistant on a tight leash against real data; and a real eval suite — I have guardrails on model output, which is a different instrument aimed at a different question, and I won’t call it evaluation because it isn’t. All specified, prioritized, and not done. Anyone can vibe-code a pile of apps; the pile of things I chose not to build yet — and the reason for the order — is the product management. It’s the part I’d rather be asked about.
- YarClaims
- Insurance claims. YarMail sends it invoices, YarDocs files them, and YarClaims keeps each claim moving. It plugs into the same rails as every other app.
- YarBucks
- Budget and expense tracking. It plugs into the same rails as every other app.