Writing
Writing
Notes on software design, distributed systems, and the operational consequences of architectural choices.
Technical notes
Operability First: Designing for Safe Recovery
Designing distributed systems so operators can determine what happened, control retries, and recover safely when normal processing fails.
Retrying OpenAI and Anthropic API Calls in Python.
A classification-first approach to retrying OpenAI and Anthropic calls safely
Safe DLQ replay checklist
A practical runbook for replaying dead-letter messages without corrupting data or melting dependencies, with SQS/SNS and Kafka appendices.
Why recourse
Policy-driven resilience for Go services: consistent retries, explicit backpressure budgets, hedging, and circuit breaking - with explainable observability.
Why redress
My retry philosophy: classification-first, bounded unknowns, capped exponential backoff, and observability hooks.