Technical blog
Engineering Thinking
Anyone can write code. Great engineers make good engineering decisions.
Latest writing
Model the Business, Not the Implementation
Optional values are useful when absence exists in the business. They become dangerous when they hide workflow state, API awkwardness, database looseness, or compiler discomfort.
Stop Using Option to Silence the Compiler
Not every 'maybe missing' value belongs in an optional type. A mental model for deciding when to reach for Option — by asking whether the uncertainty comes from reality, workflow, or implementation.
I Reduced Claude Code's Initial Context by 80% (Without Removing Any MCP Servers)
A single environment variable cut my Claude Code startup context from ~150k tokens to under 30k — and the per-session startup cost from over $1 to about $0.06.
Topics
About
This site is designed as a senior engineer's field journal: fewer hot takes, more decision records, failure analysis, architecture notes, and implementation writeups.
Posts should be useful to engineers evaluating similar tradeoffs, so the default format favors context, constraints, concrete examples, and what changed after shipping.