Articles
Dispatches from the invisible half
The half of every product nobody sees until it stops — distributed failure, data access, caching, auth. Each piece started as something that broke in production, or something I had to explain twice before it stuck.
Spending less on AI tokens without getting worse answers
Where the tokens actually go, how prompt caching silently breaks, why a precomputed code graph beats a bigger context window, and routing cheap work to cheap models.
CachingRetrievalCost
Read the piece
More articles
02
Sessions done properly
Short access tokens, refresh tokens stored as hashes and rotated on every use, theft detection that revokes a whole family, and taking permissions away without logging anyone out.
03
EF Core and SQL Server: the queries that kill you in production
The save that affects zero rows, Count versus Count(), Include chains that multiply instead of add, paging that gets slower as you page, and reading a plan without becoming a DBA.
04
Distributed systems: the parts that bite after the diagram
Partial failure, clocks that lie, why exactly-once delivery does not exist, idempotency keys, retry storms you can cause yourself in the page, and why your distributed lock is probably wrong.
05
Microservices that don't fall over
Service boundaries, the outbox and inbox patterns, the saga pattern in detail, cache stampedes, circuit breakers, and the failure modes that only show up under real traffic.
06
Agentic AI for development, from someone who built one
The tool-use loop, why context is the real constraint, how prompt caching silently breaks, and where agents genuinely help.
07
Knowing before your users do
Why averages hide your worst users, correlation ids across the broker, SLOs and error budgets, and alerts a team will not learn to ignore.
08
Docker, Kubernetes and Azure without the cargo cult
The five Kubernetes objects you really need, the probe misconfiguration that turns a blip into a crash loop, and picking the smallest service that does the job.
09
C# design patterns that still earn their place
Half the Gang of Four catalogue is now a language feature. Which ones survived, and which ones records and pattern matching quietly replaced.
10
Microfrontends: when splitting the UI is worth it
Build-time versus run-time composition, shared dependencies and version skew, who owns the URL, and the costs nobody puts in the pitch.
Ten so far, and more when something is worth writing down. If you want to argue with any of it, GitHub is the place.