The things I have been reading.

The book I keep returning to. Not because it is a revelation, but because it is honest about the limitations of any model of a complex system. Every chapter is a small reminder that the map is not the territory — and that the interesting part is usually the boundary.

Read once years ago, reread slowly this year. What strikes me now is how much of it is about affordances and how little of it is about visual style. Most of the interfaces I use daily fail at the first thing and succeed at the second.

Short, sharp, and quietly opinionated. The argument that complexity is the only real enemy — and that it accumulates one small compromise at a time — is the closest thing I have found to a first principle for technical work.

I resisted this one for years because it felt like required reading. I was wrong. It is not a style guide. It is a collection of habits, each one small enough to adopt tomorrow morning.

Uneven, occasionally brilliant. The chapter on via negativa — improving systems by removing things rather than adding them — has quietly shaped how I approach operations work.

The argument that productivity advice is usually a way of avoiding the actual question — which is what you want to spend a finite life on — landed harder than I expected. Reread twice.

A simple reframing of time as a finite count rather than an infinite budget. The kind of essay that changes one decision you were about to make.

The original 1995 lecture series. The famous question — what are the important problems in your field, and why aren’t you working on them? — is worth an entire career of reflection on its own.

Not really about code. About the idea that a principle — a thing you believe is wrong with the world — is a better compass than a career plan. I watch it once a year.