Compiled, Not Re-Derived

Knowledge you rebuild every time is rented. A case for compiling what you learn instead of re-deriving it.

In programming there's an old distinction between a compiler and an interpreter. An interpreter reads your code and works out what it means every single time you run it. A compiler does that work once, up front, and hands back something that just runs. Both get you to the same place. Only one of them stops paying the cost over and over.

Most of us treat knowledge like an interpreter. We read the article, get the gist, and move on — and the next time the topic surfaces, we start again almost from scratch, re-deriving what we once knew from whatever fragments we can still find. It feels like learning. Mostly it's re-learning.

There's another way to hold knowledge, and it looks more like compiling. Instead of re-reading the raw material each time, you process it once: pull out what matters, connect it to what you already know, flag the contradictions, and write the synthesis down somewhere you'll actually return to. The cost is paid at the moment of understanding, not at the moment of need. Andrej Karpathy framed it neatly for the AI age — the notes app is the IDE, the model is the programmer, and the accumulated wiki is the codebase. Each new source doesn't just add to the pile; it makes the whole thing richer.

Knowledge you have to rebuild every time isn't really yours — it's rented.

The difference compounds. Re-derivation scales linearly at best: ten sources mean ten separate efforts, and the connections between them are rebuilt or missed every single time. A compiled body of knowledge does the synthesis once and keeps it. The cross-references are already drawn. The tenth source lands inside a structure shaped by the first nine. You stop starting over.

This isn't really about software — it's about anyone whose work depends on understanding that accumulates over time. A salesperson is the clearest case. The rep who re-diagnoses every deal from memory and a messy inbox is interpreting: quick to start, expensive forever. The rep who keeps structured, current intelligence on each account — what's known, what's missing, who actually decides — has compiled. When the deal heats up, they're not reconstructing the story; they're reading it.

The catch is that compiling carries an upfront cost interpreting doesn't. It's slower in the moment to write the thing down, draw the link, reconcile the contradiction. That's exactly why most people skip it. But knowledge you have to rebuild every time isn't really yours — it's rented. The whole point of compiling is to own it, so the next question doesn't start from zero.