ABOUT THE SHOW
About Development Radio
A podcast for engineers who already ship backend systems and want to reason about them more carefully, from a Redis lock that expires mid-checkout to the review that never credits the work keeping releases moving.
What is Development Radio?
A podcast about advanced backend engineering and the judgment around it. Each episode follows one concrete system, such as a Redis lock that expires while its holder is paused or a read replica a few seconds behind, until the tradeoff is clear and you have one thing to try at work.
Who is it for?
Backend engineers who already run production systems and want to reason more carefully about concurrency, data correctness and change; Senior engineers growing toward Staff; and technical leaders who make or review these decisions.
What topics does it cover?
Distributed locks with Redis and Postgres, queue fairness and worker pools, read replicas and replication lag, OFFSET and keyset pagination, migrations and rollback, retries and idempotency, technical debt, glue work, and real AI and security stories from the week.
How long are the episodes?
Daily episodes run about 3 to 10 minutes and stay with one question. Weekly episodes run about 10 to 40 minutes.
Who hosts it?
Two recurring hosts, Maya and Alex. Maya keeps asking who feels the consequence; Alex brings the wider tradeoffs and a plan for when a design meets reality. The show is created by Dorel, a Staff Engineer with a focus on backend systems, production engineering, and helping people grow.
Where should I start?
Pick a track on the Start here page. For a single first episode, try Redis Locks: When the Old Request Wakes Up.
Where can I listen?
On this website, Apple Podcasts, Spotify, YouTube, Pocket Casts, Podcast Addict, or any podcast app through the RSS feed.
Can I check the sources?
Yes. Every episode page lists its sources and chapters and includes a full timed transcript.
YOUR NEXT GOOD LISTEN