what should I
write next?
Half-baked post pitches. Vote on the ones you'd actually read — I commit to writing the top two. I don't want your data. Just click the buttons. Spam it if you have to.
observability for LLM apps without losing your mind
What traces actually buy you when half your stack is non-deterministic, and the patterns that hold up in production.
shipping software with a brain that fights you
Late-diagnosis ADHD, twenty years of compensating, and the workflows that actually stuck.
small multi-agent systems for personal use
What you can actually build in a weekend with claude code + a few cheap tools. The boring wins matter.
platform engineering in the AI era
How the abstractions we shipped to support microservices break (and adapt) under agent workloads.
designing a shadowrun-flavored dev tool
A design walkthrough of this site — picking a palette, killing generic AI aesthetics, and making something that looks like you mean it.
what Philip K. Dick taught me about systems
Reality is software. Software is reality. A meditation on building things that get further from the metal every year.
kill your monitoring, keep your signals
Most dashboards are noise. A taxonomy of what to delete first, and what to keep no matter how loud it gets.
what 30 years of tabletop RPGs taught me about engineering teams
Rulebooks, session zero, encounter design — the GM playbook maps onto leading engineers better than most management books.
votes are stored in a Cloudflare KV namespace and counted once per browser per pitch.