Reed–Solomon Erasure Coding Without the Magic
Build a tiny Reed–Solomon code step by step, erase half its shards, and recover your own input without treating the maths as magic.
Tag: reliability
6 posts in this channel.
Most Race Conditions Are Ownership Problems
Before adding a lock, decide which operation owns the right to commit a result and when that ownership expires.
The API Returned 200. The Operation Still Failed.
HTTP success, application success and business success are separate outcomes. Clients need to check the one they actually depend on.
Logs Are Not Observability
Producing more log lines does not make a system easier to understand. Start with the questions an operator must be able to answer.
Timeouts Need a Deadline, Not Just a Number
Giving every operation its own timeout can make one request take several times longer than intended. Pass the remaining deadline instead.
Queueable Apex That Survives Retries
Queueable Apex becomes reliable when jobs are treated as at-least-once work: use idempotency keys, durable checkpoints, bounded retries, and outcomes you can inspect.