This is a guided series through the most important papers in software systems.
It’s not just a list. It’s a deliberate path — starting with how we think, and building up to how we coordinate machines around the world.
Each paper shaped how we build today’s infrastructure. These writeups unpack not just what the paper says, but why it mattered — and still matters.
The posts below appear in publication order. If you’re looking for a suggested reading path, start here.
More than a design guide, the Reactive Manifesto triggered a shift in how developers approach time, failure, control, and team dynamics. This post traces its deeper impact — across technical, philosophical, psychological, and cultural lines.
Behind every new language is an old idea we forgot to name. This post explores how Landin’s paper helped us see code as scaffolding for thought — and why that lens still matters.
This post explores the deep impact of Moseley and Marks’ work on software architecture, drawing out its technical, historical, philosophical, and cultural significance.
This isn’t just about one paper. It’s about the shift it caused — from chasing tools to understanding systems, from hoping for miracles to working with reality.
A deep dive into Richard Gabriel’s provocative thesis — and why software that survives often starts simple, flawed, and just good enough.