vol. 02 · spring 2026
An engineering notebook — small fixes, environment tricks, and the patterns I keep reaching for.
Kubernetes, AWS, dev environments, and the occasional deeper essay. Each entry is a problem I had, the fix I landed on, and why it works — written so future me can find it again.
This month's essay.
long-form · once a month · ish fig.001 — infrastructure
The problem
A 500 in a service that calls two others means three separate log streams and no common thread. A correlation ID that flows through every hop automatically — via the W3C traceparent header — collapses the entire trace into a single query.
read the full essay →