01Essay
Silent Defaulting
A system cannot tell nobody told me from they told me a legitimate value. So it picks a default, carries on, and produces a wrong answer with no error anywhere.
A system cannot tell nobody told me from they told me a legitimate value. So it picks a default, carries on, and produces a wrong answer with no error anywhere.
I replayed two months of history into a system and every event arrived stamped with the moment of the replay. The data was perfect. The time was fiction. Nothing complained.
Your issue tracker is a distributed system with one replica per engineer and no consistency guarantee. It drifts from reality quietly, and then you plan against it.
A slide from 2019, a catalog that lied politely, and one engineering question that kept surviving every change of system.
A maintenance window is a confession: somewhere, an operation was never made bounded, observable, or abortable. What rebalancing 50,000 Kafka replicas taught me about removing the confession.
Availability, designed from a place where the power grid is part of your threat model. Reliability lessons the textbooks cannot teach.
Publishing in order as each is finished. Subscribe and they arrive the day they land.
When Health Checks Lie: Anatomy of a Cascading Failure
A 200 proves a process is alive. It proves nothing about whether the work it is doing is correct, and that gap is where cascades are born.