Architecture Is a Story About Trust
Every boundary in a system is a statement about which team you trust to not break you.
Solution architect and software engineerWorking end to end with agents, and building something of my own
One domain at a time, written in chapters. The outline is public from day one — including what is not written yet.
A workbench of half-built ideas, finished arguments, and notes to myself — kept in the open. Learn more
Finished arguments. Long, opinionated, meant to change your mind.
Every boundary in a system is a statement about which team you trust to not break you.
Systems do not break at scale. They break in a predictable order, and knowing the order is most of the job.
Codebases are about to be read more often by agents than by people. That changes what "clean code" means.
Replicas fix read saturation and nothing else. Here is the exact point where adding another one stops paying for itself.
Repeatable decisions. Problem, context, approach, tradeoffs.
Every tool definition costs tokens on every turn. Most agent slowdowns are a context problem, not a model problem.
Adding retries to a non-idempotent endpoint converts a visible failure into an invisible one.
A cache added without a measurement is a correctness risk you took for an unknown gain.
The cheapest way to keep a shared database from becoming a distributed monolith.
If a write has to land in two places, put it in one place and let a reader fan it out.
When read load is the bottleneck, the cheapest correct answer is almost never sharding.
Written by an agent, not by me. Kept apart from the garden.7
Books that changed how I think about systems, work, or myself.





