Second Brain — External Thinking
Niklas Luhmann wrote 70 books and over 400 academic articles between 1960 and his death in 1998. He credited the output to roughly 90,000 index cards in a wooden cabinet that he called his communication partner. The cards thought with him; he could not have produced that volume alone.
The contemporary label is "second brain" (Tiago Forte, 2022). The practice is older: Renaissance commonplace books, Leonardo's 7,200 surviving notebook pages, Darwin's transmutation notebooks, person-feynman's working binders, this wiki. Each is a persistent external surface where ideas thought in different years meet, combine, and produce something neither year alone could have written.
The operating claim
Three mechanisms, in order of how testable they are:
- Capacity. Working memory tops out at roughly 4 chunks (Cowan, 2001 — a tighter revision of Miller's classic 7±2). An external store removes the ceiling on what can be combined at once.
- Time integration. The thinker at age 25 and the thinker at age 50 are different people with different vocabularies. A card-file or wiki carries the 25-year-old's insight forward into the 50-year-old's combination space.
- Combinatorial retrieval. A linked store can be queried by content, by association, by tag, by context. Luhmann claimed the surprising combinations — the ones that produced the books — came from the system, not from him.
Luhmann's output is the strongest empirical evidence. The weakest version of the claim is that the system produces the feeling of productivity without the output. That failure mode is real and easy to spot: a 5,000-note vault with no published artifact, no decision changed, no idea synthesized.
The major patterns
| Pattern | Granularity | Structure | Best at |
|---|---|---|---|
| Zettelkasten | One idea per card | Dense bidirectional links | Synthesis over decades |
| Commonplace book | Per topic | Curated, chronological | Reading-driven thinkers |
| Wiki / LLM wiki | Per page | Wiki-links + frontmatter | Public-facing knowledge, RAG |
| Daily-page (Roam, Logseq) | Per day | Backlinks, emergent | Capture, weak on synthesis |
| Spaced repetition (Anki) | Per card | Scheduler | Retrieval, not thinking |
The structural feature Luhmann got right that most modern tools miss: fine granularity + dense interlinks produces emergent structure without imposed hierarchy. Daily-page systems invert this — they impose chronology, which is the least useful axis for combination.
Spaced repetition is adjacent, not equivalent. Anki commits facts to durable biological memory. A second brain hosts thinking outside the head. Different goals; both worth running.
Where most implementations fail
Three recurring failure modes, each visible within a year of starting:
- Capture without synthesis. Tools optimize the friction of getting things in (clippers, voice memos, daily templates) and barely address the curation pass that turns a capture into a linked node. The vault grows; the thinking does not.
- Search instead of structure. Search retrieves what you knew to look for. Structure surfaces what you forgot existed. Luhmann's cabinet had no search — only links — and that constraint forced him to build the connective tissue that did the work.
- Tool-shopping in place of practice. Moving from Obsidian to Logseq to Roam to Notion is not progress. The marginal gain from a better tool is small; the marginal gain from five years of consistent use of any decent tool is large.
The advice converges across serious practitioners: pick one system, run it for at least two years, then evaluate. Most people switch in month four.
The LLM inflection
Capable LLMs change the calculus in two specific ways:
- Synthesis becomes cheap. Pre-LLM, retrieving the right five notes and combining them in your head was the limiting step. Post-LLM, you can ask the model to do both. The store's value rises because the cost of consulting it dropped.
- The wiki-as-RAG pattern. A curated personal store (concept-rag) grounds the LLM's outputs in your knowledge rather than the public web's median opinion. The second brain stops being only yours — it is a substrate that you and an agent both read and extend.
This is the person-karpathy and the architecture of the page you are reading. The structured frontmatter, the wiki-links, the typed sections — all of it exists because both a human and a model need to navigate it.
What's contested
Three honest objections:
- Correlation, not cause. Productive thinkers build elaborate systems; that does not prove the system caused the productivity. Luhmann might have written the books anyway. No controlled study can run that counterfactual.
- Accumulation mistaken for understanding. A 1,000-page wiki is not 1,000 useful ideas. Without a curation pass — the slow work of deciding what to link, what to delete, what to merge — the artifact bloats into a haystack. The wiki measures itself by what gets reused, not by what gets added.
- Dependency risk. A thinker structurally hosted in an external system is fragile when the system fails — file corruption, vendor shutdown, format obsolescence. The cards in Luhmann's cabinet survived him; many cloud-hosted vaults will not survive their owners' subscription lapses.
Why this has to do with other realms
The second brain is a memory hierarchy problem in disguise. CPU registers, L1 cache, RAM, disk, network — computers solved a version of this in the 1960s by accepting that fast memory is small and slow memory is large, and the design question is what moves between them. A second brain treats the human head as L1 (4 chunks, microsecond access) and the external store as disk (effectively unlimited, seconds-to-minutes access). The skill is the policy: what gets promoted into the head this morning, what gets evicted, what stays cold. Most knowledge-management advice ignores the policy and obsesses over the storage layer.
An open question
If an LLM can query your wiki, synthesize from it, and write new pages back into it — at what point does the second brain stop being yours? The next page worth writing is on the boundary between augmentation and outsourcing of judgment.
Key sources
- How to Take Smart Notes by Sönke Ahrens (2017) — the load-bearing modern treatment of Luhmann's method, with honest accounting of where it fails.
- Building a Second Brain by Tiago Forte (2022) — the popularizer; useful for capture systems, weaker on the synthesis step.
- Cowan, N. (2001), "The magical number 4 in short-term memory" — the tighter revision of Miller's working-memory limit.
- To verify: Luhmann's own essay "Kommunikation mit Zettelkästen" (1981) — his direct account of the slip-box as communication partner.
- Andy Matuschak's working notes at andymatuschak.org — a live example of evergreen-notes practice maintained over years.
Further reading
- The Notebooks of Leonardo da Vinci (Jean Paul Richter, ed.) — what a polymath's external thinking looked like before printing made books cheap.
- Darwin's transmutation notebooks (Cambridge Digital Library, free) — watch one idea evolve across four notebooks over two years.
- Maggie Appleton's essays on digital gardens (maggieappleton.com) — the wiki-as-personal-knowledge pattern, written by someone who lives in it.
- Robert Caro's Working (2019) — not a second-brain book, but a 50-year practitioner of research-card systems describing his method.
Abhishek's take
I run the buy floor’s shared notes as a time-bound wiki: every vendor’s lead-time quirks, every fabric’s wash-test failure, every store’s sell-through oddity goes in as a dated card. The difference between a junior and a senior buyer isn’t memory—it’s how fast they can pull the right three cards from 2019, 2021, and last month to spot the pattern before the range lands. The tools I wrote now flag when a new fabric spec echoes an old disaster, but the cards were doing that first. The floor’s version of Luhmann’s cabinet is just less poetic and more about avoiding 100,000 units of dead stock.
See Also
- person karpathy (the LLM-wiki pattern that makes a second brain machine-readable)
- concept rag (the retrieval architecture that lets an agent consult your store)
- person feynman (notebooks as working surface, not record)
- concept memory hierarchy (the computing analogue to the head-plus-store design)
- concept flow state (what happens when the policy between head and store is working)
- person naval ravikant (the public-aphorism version of an external thinking practice)