Stop Organizing the Books You’ve Read

I’ve kept a list of books I’ve read for about fifteen years. The list grew. My understanding of any particular topic didn’t grow at the same rate. For a long time I thought this was a discipline problem — I wasn’t taking good enough notes, wasn’t reviewing them, wasn’t picking the right books. None of those fixes changed the underlying ratio.

Eventually I started suspecting the frame was wrong.

The book is a very persuasive unit of organization. It comes in a physical container with a title and a spine. Libraries are organized around it. Syllabi assign it. “Books read this year” lists assume it. So it’s natural to conclude: if I take better notes per book, and keep them tidier, my understanding will be better organized too.

But the thing I actually wanted from reading — the thing I think most serious readers want — was never the book. It was the idea inside the book. And ideas don’t honor the boundaries of the volume they happened to arrive in.

Take any concept you’ve thought about for a while. The version of it sitting in your most recent book is rarely the most useful version. The useful version is composed: a piece from something you read in college, a paragraph from a novel you didn’t even think was related, a remark from a conversation last March, and yes, something from this book too. Understanding lives at the intersection, not in any one of them.

This is what the shelf cannot help with. A perfectly organized shelf — alphabetical, color-coded, divided by genre — still leaves the ideas inside each book locked behind a cover. The shelf was never the unit. The idea was.

This is, in the end, why I’m building Linko.

I don’t think the value of a reading system is in helping you remember books. Memory is a side effect of something more important: connection. When a half-sentence you wrote about anchoring weeks ago surfaces next to a new note about how a designer frames a price page — that’s where understanding actually compounds. Not in the act of saving. In the moment the two find each other.

We’ve called the structure underneath this a Knowledge Tree, though the word tree is a little misleading — it sounds too tidy. What it is, in practice, is a slow-growing network of your own thoughts, where the system’s job is to notice when two of them are about the same underlying thing and put them within reach of each other. AI here isn’t a writer or a thinker. It’s closer to a gardener. The thinking is yours. The remembering across years is the part you cannot do alone.

What changes, when this is in place, is small but significant. “What should I do with this book once I’ve finished it” — a question with no good answer, because books don’t have a natural next step — becomes “where does this idea connect to what I’ve already thought.” That one has an answer almost every time. And it tends to produce the kind of returns reading is supposed to produce: a slowly thickening understanding of a few things you care about, instead of a longer list of titles.

I still keep the list. It’s mostly nostalgic now. The real archive isn’t the books I’ve read. It’s the network of ideas they left behind, finally able to talk to each other.