Decisions, lessons,
and the occasional argument.
Essays written while building: how we decide what's worth doing, what we turned down and why, and what the tools taught us. Judge the thinking for yourself.
Start here
How we approach a business problem
Technical depth, for builders
The wider view
All posts, newest first
Nutrition Labels for Software
One small file per question you have at adoption time: what an app is built from, what it can do, what it touches. Some labels fit any software, others cover the AI layers. We ship them on the tools we publish. Hub at xfacts.dev.
What Over How
The kickoff ends early. Everyone nodded at modernize. Three people just heard three different projects, and nobody finds out until month four.
What We Didn't Build
We shipped Exec Foundry, a search workspace for senior professionals. The obvious feature we turned down says the most about how we build.
Wielding the New Fire
Fire is the lens I use for AI: a primitive, not a tool, and one that became widely accessible faster than we learned to use it well. Most people are still using it to keep the animals away.
Prompts Aren't All You Need
Every workaround you write is a bet against the next model. The work moved off the prompt and into the architecture around it.
AI Just Changed. Most People Missed It.
A February 2026 reaction to one viral post, kept as a dated perspective: what Shumer claimed, why it mattered for your business, and five things to do about it.