What Is a Second Brain?

A second brain is a personal system for capturing, organizing, and retrieving the information you encounter, so your knowledge keeps compounding instead of evaporating after a week. The phrase was popularized by Tiago Forte's 2022 book Building a Second Brain, which turned the loose idea of an external memory into a concrete workflow anyone could copy. The concept is tool-agnostic, but the app you pick decides whether your second brain actually outlives the product it lives in.

The problem a second brain is meant to fix

You read an article that explains the thing you were stuck on. You highlight it, close the tab, and six weeks later it's gone. You bookmarked it, probably, or saved it to a read-later app, or pasted the paragraph into a Slack message to yourself. It doesn't matter. It's gone.

The second brain is the name for the fix.

Where the idea comes from

The phrase "second brain" in its modern sense comes from Tiago Forte, a productivity writer whose 2022 book Building a Second Brain packaged an older intuition into a workflow you can actually follow. The older intuition traces back to Vannevar Bush's 1945 essay "As We May Think", which imagined a desk-sized machine called the Memex that would extend a reader's memory through linked microfilm records. Bush couldn't build the Memex. Forte's book arrived at the moment the tooling finally caught up, and most of the modern framing below comes from his overview essay at Forte Labs.

At the level of daily practice, a second brain is a single trusted place where you send the things you want to remember. That's it. The trusted place is usually a note-taking app. The things you send are whatever doesn't fit in your head, like an article you want to come back to, a quote that changed how you think about a problem, a decision you want to remember the reasoning for, or a fragment of an idea you haven't figured out yet.

What makes a second brain different from a folder of screenshots is that you process what you save. You come back later, pull out what's actually useful, and leave notes for future-you. Over time the system gets denser, not bigger.

Why the idea caught on now

The information you encounter in a week outpaces what you can remember in a month. That ratio has always been bad. It got worse when the web turned every article, PDF, and forum post into a browser tab away, and nobody reads 200 newsletters with full recall. The cost of knowing you saw something but not being able to find it compounds every year.

What changed recently is the tooling. Full-text search, portable markdown, fast local storage, and cross-device sync finally arrived in the same products at the same time. Forte's book landed at the moment a generation of power users were already trying to figure out what to do with all the notes they'd been hoarding, and it gave them a vocabulary for doing it on purpose.

CODE, in one breath

Forte's framework is called CODE. It's four verbs, and this is the part of the book you'll see quoted everywhere.

Forte pairs CODE with the PARA method, an organization system where every note lives in one of four places, Projects, Areas, Resources, or Archive. Most people spend their first month arguing with PARA. That's fine. The method is load-bearing only until you figure out your own version of it.

What most second brain guides skip

Most second brain tutorials stop at the workflow. Pick an app, set up your folders, start capturing. They don't talk about what happens to your brain when the app changes its pricing, breaks its export, or shuts down.

That omission is expensive. In November 2023, Evernote capped its free plan at fifty notes and a single notebook after years of stable pricing, which left long-time free users with thousands of notes locked out of adding new ones unless they upgraded. Notion has a different problem. Its export is lossy because the internal data model is richer than markdown, and databases come out as CSV, callouts and toggles get flattened, and linked pages end up with paths that break the moment you rename a folder. These aren't bugs. They're the shape of the products.

If you're going to pour a decade of reading, thinking, and project notes into a single system, three questions decide whether the investment holds up.

Where does your data live. On your device, on a server you control, or on a company's cloud bucket? If the company goes under, can you still open your notes?

What format is it in. A format you can read with a text editor in twenty years, or a proprietary database only the vendor knows how to parse?

How does it sync. On a protocol you can swap out, or baked into the app so tightly that leaving means starting over?

None of these are philosophical questions. They decide whether your second brain is a real long-term investment or a rental.

How to pick a second brain app

Here's the honest comparison of the apps most people end up choosing.

Pick based on which question matters most to you. If your main worry is that the app you pick should outlive the data you pour into it, Obsidian and Logseq are the safe picks, because the notes on disk stay as plain markdown the day the company disappears. If you want power and you're willing to trade portability, Tana and Roam give you a graph that feels magic as long as you stay inside their app. If you already live inside Apple's ecosystem and only need capture, Apple Notes is the lowest-friction default. If you want databases and team features, Notion is still the easiest entry point, and you should plan for the export story from day one.

If I weren't building CoCube, I'd be back in emacs org-mode, trying to get it working again. Org-mode is the most extensible second brain tool that exists if you're a programmer, and the keyboard-driven workflow is the reason I still miss it. What broke it for me was the same thing that made me love it. I kept extending it to automate more of my system, and every layer of custom elisp was one more thing that could fail at the wrong moment.

How CoCube fits the second brain model

CoCube is built for the version of this problem where portability and programmability both matter.

Every CoCube document is stored as a Loro CRDT in a local database on your device. Your second brain reads and writes at local-disk speed and keeps working when you're offline. The sync layer ships binary deltas between devices you own, which is the same model described in the local-first software article. The format is documented. You can open it on another machine, or hand it to a future tool that reads the same CRDT.

What makes CoCube different from the other local-first options is that the system itself is programmable. A note isn't a markdown blob, it's a tree of typed cells you can wire together into small components. You can build your own capture form, your own distillation view, your own project tracker, all in the same document model as the notes. That's the same idea explored in the visual programming language post.

CoCube isn't a drop-in Obsidian replacement today. If your current second brain is a pile of markdown files with backlinks and you want to switch tomorrow, Obsidian or Logseq is still the closer match. CoCube is the version of this workspace where your system can grow into its own personal software, and where the data underneath stays yours the whole time.

What to read next

A second brain is only as durable as the format it's written in. Forte's book is the right introduction to the practice. The seven ideals of local-first software, especially the fifth ideal about the long now, are the right framework for picking an app you won't regret in a decade. If you want to go one layer deeper on the sync technology, the CRDT article is the next stop. The larger practice a second brain slots into lives in the PKM guide, which is the pillar for this cluster. If you want to see how CoCube's cell model connects to the spreadsheet you already know, the reactive programming post explains that bridge. The vision behind why CoCube exists lives in the composable software post. For a practical comparison of tools, the Obsidian alternatives and Notion alternatives roundups are the place to start.

Pick the app you'll still be able to open in 2036.