#651 – November 09, 2025
The domain name system turned 40 this year
A brief history of domains
11 minutes by Pete Millspaugh
The domain name system turned 40 this year, starting with the first domain registration in 1985. Since then, nearly a billion domains have been registered across hundreds of extensions. The system has evolved from a small academic project to a massive global infrastructure. Pete takes us on a tour of domain milestones over the last forty years.
How Cursor, Intercom, and Cash App scale their databases
sponsored by PlanetScale
PlanetScale offers the fastest Postgres and MySQL available in the cloud. Blazing fast performance, ultra low-latency, unlimited IOPS, 99.999% uptime - all fully managed and available in AWS or GCP. Experience why companies like Cursor, Intercom, and Cash App choose PlanetScale to power their databases.
Why your computer finds things faster than you
15 minutes by Deyaa Al-Khatib
Deyaa built a binary search tree for a file project and watched it collapse when simulating real disk operations. While binary trees work well in memory, they require too many disk reads for large datasets. B-trees solve this by storing many keys per node, fitting entire nodes into single disk blocks. This reduces searches from 20 disk reads to just 3, explaining why all major file systems and databases use B-trees instead of binary trees.
Use Postgres until it breaks
33 minutes by Stanislav Kozlovski
Modern hardware is powerful enough that simple solutions often work better than complex distributed systems. Stanislav benchmarks Postgres for pub-sub messaging and queueing, showing it can handle most real-world workloads effectively. Use it and reach out for specialised tools when it breaks.
Reproducing AWS outage with model checker
8 minutes by Waqas Younas
Waqas examines a race condition that caused an AWS outage using formal verification. He recreated a simplified version of the DNS management system problem using the Spin model checker and Promela language. Two DNS Enactors running concurrently caused issues when one applied a newer plan while another applied an older plan that was then deleted during cleanup. The model checker successfully identified this race condition by testing system invariants.
How I use every Claude code feature
16 minutes by Shrivu Shankar
Shrivu deep dives into Claude Code—what works, what doesn’t, and how it fits into real workflows. From months of daily use across side projects and enterprise systems, he looks into CLAUDE.md, hooks, subagents, and planning tools. Rather than chasing model benchmarks real productivity comes from structure, clarity, and disciplined context management.
And the most popular article from the last issue was: