NEW HERE?
Start here: a listening path for backend engineers
Each episode follows one concrete system until the tradeoff is clear, then leaves you one thing to try at work. Pick the track closest to what you are dealing with this week.
TRACK 01
Concurrency: locks and who goes next
A Redis lock expires while its holder is paused, and one concert seat is sold twice. Follow it to the database condition that refuses the late write, then ask what fairness means when every worker is busy.
daily · 9:01
Redis Locks: When the Old Request Wakes Up
The full seat-14C story, with room to follow it. Start here.
daily · 9:36
Queue Fairness: Who Gets the Next Worker?
Shared worker pools: protect capacity, or lend idle workers and accept the pause?
TRACK 02
Data correctness: replicas, reads and pagination
A save succeeds but the preview shows the old value. A report finishes but slows everything sharing its database. Two everyday surprises, traced to which copy you read and how you reach the next page.
daily · 4:20
Read Replica Lag: You Saved It. Why Did It Disappear?
Read replica lag, and which reads must include your write.
daily · 4:17
The Report Works. Is All That Database Work Necessary?
OFFSET pages, keyset pages and the work a report really needs.
TRACK 03
Changing production safely
A rollback that cannot undo data, a timeout that may already have succeeded, a retry that sends a report twice. How to rehearse a change, and how to pick the repair that matters.
weekly · 10:42
Before You Migrate: Can You Really Roll Back?
Migration rollback, unsafe retries and idempotency.
TRACK 04
Staff-level judgment
The work that keeps releases moving rarely shows up in a review. Credit it, hand it off, or both, and who pays for the handoff?
daily · 8:15
Invisible Engineering Work: Why Every Release Still Waits for Her
Glue work, release handoffs and what counts in a review.
TRACK 05
This week in AI and security
Real stories from the week, explained for engineers, each with a Hype-or-Real verdict.
weekly · 35:49
AI Got Faster This Week. Every Story Still Came Down to a Person.
A CA key that was 4, a poisoned LiteLLM release, and agents that muted their own alarms.
TRACK 06
More conversations
Newer episodes, not yet placed on a track.
daily · 13:22
This Certificate Authority's Private Key Was the Number 4
"Enterprise Digital Trust, Ready for the Quantum Era." That's eMudhra's homepage. One of its intermediate CA private keys was the number 4.
daily · 10:49
Meta's AI Chat Links Leaked Through DNS
"Anyone with the link can view." Meta's new AI agent Muse put each shared chat's title into its web address, and a security firm found more than 6,800 of those names in one passive DNS search. Then the AI heist of the week: OpenCode says provider keys saved in its Console may have been exposed, and some users reported surprise bills of more than $1,700 overnight. OpenCode called it a large-scale distillation attack; nobody has said who did it. Separately, Anthropic alleges that Kimi's maker quietly sent user requests to Claude and served the answers as Kimi's.
daily · 8:18
Multi-Zone Failover: Healthy Servers, Stuck Jobs
Three zones. Available workers. A new import that cannot start. Google’s preliminary London outage report opens a deeper question: which required answer still comes from the place you just lost?
daily · 9:01
PostgreSQL Backups: Why Completed Can Still Mean Broken
In our worked example, the latest PostgreSQL backup completed. Restoring it stops on a page-checksum error that was already recorded overnight. What exactly did that successful backup prove?
YOUR NEXT GOOD LISTEN