NOT MINE
This is just a reference/bookmarked article from the internet i found interesting!
The Second Brain Delusion: Why PKM Systems Don’t Work
Hi, I’m Jay. I take things to 35,000 feet for a living or at least I will, once I finish flight training. (This year alone I’ve logged 10 flights and it’s only October.) I’m also a psychology student and a blogger, which means I have a professional obligation to overthink everything.
The first time I opened Obsidian and saw the graph view a black cosmos waiting to be filled with stars I felt a jolt of pure possibility. Here was the answer. As a psychology student drowning in textbooks and studies, a cadet pilot wrestling with dense manuals and checklists, and a blogger trying to find a unique voice, I was a sinkhole for information. The promise of a “second brain,” popularized by sleek YouTube videos and compelling courses, wasn’t just attractive; it felt like a necessary evolution.
For those who haven’t explored it, Obsidian’s graph view looks like a spider web network of notes impressive at first glance, almost profound. But spend a moment with it, and you realize it’s more like a messy web of ideas, where connections exist, but not always in the way you expect.
I would build my digital exo-cortex. It would remember every citation, every procedure, every fleeting idea. It would connect a concept from developmental psychology to a principle of aerodynamics and surface the insight just as I needed it for a blog post. I envisioned a seamless fusion of my disparate worlds.
I embarked on the build with fervent dedication. Evenings vanished into the rabbit hole of plugins, CSS snippets, and elaborate dashboards. My vault was a temple of organization: folders, a rainbow of tags, and notes filled with meticulously pasted quotes and article summaries.
My vault was glowing blue with connections, but I couldn’t remember what half of them meant. I stared at the graph view like a patient staring at their MRI scan, seeing everything and understanding nothing.
The Psychology of the Build: Why We Fall for the Trap
My initial months with the system were fueled not by genuine learning, but by a cocktail of powerful psychological biases. I wasn’t building a brain; I was acting out a script written by my own cognitive wiring.
The IKEA Effect & Effort Justification: I had sunk dozens of hours into building my system. I’d crafted the perfect templates, color-coded my tags by domain, and mastered the keyboard shortcuts. This investment wasn’t a sunk cost; in my mind, it was proof of the system’s inherent value. The more laborious the build, the more indispensable it felt. I was overvaluing my creation simply because I had built it. Critiquing its utility felt like critiquing a part of myself.
Cognitive Offloading & The Zeigarnik Effect: There’s a deep, psychological relief in capturing a thought. The Zeigarnik Effect tells us that unfinished tasks create psychic tension, occupying valuable mental real estate. Writing a thought down in a “trusted system” provides closure. I felt this relief constantly. Jotting down a book quote or saving an article felt like progress. I was offloading memory, and my brain, grateful for the space, misinterpreted this relief as learning. I was confusing the act of emptying my mental pockets with the act of examining the treasures inside. The tension was resolved, but the understanding was deferred, indefinitely.
The Collector’s Fallacy: This became my primary sin. I was a digital dragon atop a hoard of gold I never spent. My vault swelled with hundreds of notes: summaries of Piaget’s stages, explanations of Bernoulli’s principle, highlights from marketing blogs. The activity of collecting felt intensely productive. I was “doing something” about my information intake. But mastery? Insight? They were nowhere to be found. I had fallen for the fallacy that amassing information is synonymous with understanding it. My vault was a museum of other people’s ideas, and I was a sleepwalking curator.
Productivity Theater: This was the ultimate outcome. I’d spend a three-hour study session where 90 minutes were devoted to finding the perfect structure for my notes on cognitive biases, adjusting headers, and creating internal links. It looked like work. It felt like work. But it was a performance an elaborate play with no audience but myself, where the stage management replaced the actual play. I was practicing the illusion of scholarship.
The Cracks in the Foundation: Where the Metaphor Breaks
pexels samuel jeronimo 85164918 20112056
After the initial euphoria faded, a low-grade frustration set in. The system wasn’t doing anything. The promised insights weren’t emerging. The graph view, once a source of inspiration, began to look like a map of my confusion. This wasn’t a failure of the tool, but a failure of the core metaphor.
The Brain-as-Storage Fallacy: I had fundamentally misunderstood how my own brain works. I’d treated it as a faulty hard drive, and my notes app as a perfect, external backup. But neuroscience shows us that memory is not static; it is reconstructive. The power of a memory isn’t just in the stored fact, but in the rich, associative network of connections that surround it the context, the emotion, the smell of the room when you learned it.
By outsourcing memory to a passive, static vault, I wasn’t enhancing my memory; I was starving it. I wasn’t building those neural pathways. I was simply creating a crutch that ensured I’d never learn to walk on my own.
Apophenia & The Illusion of Insight: Obsidian’s auto-link feature and graph view are seductive. I’d see a note on “stress” from psychology autolink to a note on “stress” on an aircraft’s airframe. My patternseeking brain (a phenomenon known as apophenia) would jolt with excitement. “A connection!” it would scream. But the system wasn’t intelligent. It didn’t understand that one was a psychological state and the other a physical force. It was merely matching a string of characters. I was imbuing a mechanical, syntactic process with semantic meaning, fooling myself into believing I’d had an insight when I’d merely witnessed a coincidence.
Confirmation Bias in Linking: Even when I made links manually, I wasn’t immune. I realized I was preferentially connecting ideas that already agreed with each other, building an echo chamber of my own preconceptions. My network wasn’t challenging my thinking, it was reinforcing it. A true thinking tool would surface disconfirming evidence, but my system was designed by me, for me, and was subject to all my blind spots.
Cognitive Load & Maintenance Overhead: The system, designed to reduce cognitive load, became its primary source. The “maintenance cliff” is real. The first 100 notes are fun. The next 500 are a nightmare. I’d create a tag called ” cognitive-bias,” only to later decide ” bias ” was a better structure. I’d spend entire sessions “refactoring” my vaultretagging, relinking, reorganizinginstead of engaging with new ideas. The tool meant to free my mind had become its most demanding taskmaster.
The Turning Point: From Archive to Logbook
The shift happened slowly, then all at once. I was preparing for a crucial flight exam and simultaneously writing a blog post on the psychology of stress and performance. I had all the ingredients: notes on YerkesDodson law, on aviation emergency procedures, on studies about working memory under pressure. Yet, I was stuck. My vault was a library of answers, but I had forgotten my original question.
Frustrated, I did something radical. I closed all my other notes and opened a blank one. I titled it “What do I actually think about stress and performance?” I didn’t paste a single quote. I started writing in my own, clumsy words. I connected the cold, clinical facts from my notes to the hot, visceral fear I’d felt during a simulated engine failure. I argued with myself. I asked questions I didn’t have answers to.
In that moment, I stopped being an archivist and became an architect. I wasn’t storing knowledge; I was building understanding. This single note, messy and personal, was worth more than the hundred perfectly formatted notes it linked to.
I had discovered the key: my second brain wasn’t a knowledge archive; it was a thought logbook.
The difference is everything:
- An archive values completeness and fidelity to the source. A logbook values clarity and fidelity to your thinking.
- An archive is passive and retrospective. A logbook is active and prospective; it’s where you think about what’s next.
- An archive is about them. A logbook is about you.
My Three Rules for a Thought Logbook
- The Input Tax: For every piece of external information you save, you must write one sentence of your own original thought, question, or reaction.
- The Title is the Thesis: Every note title must be a full sentence that states a clear claim or idea (e.g., “Performance anxiety is a feedback loop between physical symptoms and cognitive appraisal” instead of just “Performance Anxiety”).
- Link with Verbs, Not Just Nouns: When connecting notes, describe the relationship. This note contradicts that one. This note is an example of that one.
The Future: Towards a True Thinking Partnership
The next evolution lies in AI and Local LLMs. Imagine not just manually linking your note on “cognitive load” to your note on “cockpit design,” but being able to ask your vault: “Find all implicit connections between my notes on cognitive psychology and my notes on aviation safety, and draft a brief on how to design cockpit systems that reduce pilot error.”
A local, private AI model could act as a research assistant trained exclusively on your unique knowledge base. It could:
- Surface non obvious connections across domains (e.g., linking a concept from music theory to a problem in software design).
- Act as a devil’s advocate, challenging your arguments by surfacing your own notes that contain contradictory evidence.
- Generate summaries and outlines from the tangled web of your own thoughts, helping you move from collection to creation.
This wouldn’t replace thinking; it would augment it. The AI would handle the bruteforce work of searching and pattern recognition across a vast dataset (your vault), while you, the human, would provide the judgment, intuition, and creative spark. This is cognitive symbiosis or as a good Reddit friend said a cognitive exoskeleton.
Conclusion: The Scaffolding and The Architect
pexels suzyhazelwood 1887609
My journey through the hype cycle of the “second brain” taught me a humbling and uncomfortable truth: the entire metaphor is a lie.
Not a useful simplification. Not an imperfect analogy. A lie.
You don’t need a second brain. You have a first brain that thinks, and a filing cabinet that doesn’t. Calling it a “brain” was just clever marketing and excellent framing. A way to sell note-taking apps and courses by wrapping an ancient practice (keeping a commonplace book) in the seductive language of cognitive enhancement.
Even as a Personal Knowledge Management System, the concept is fundamentally flawed. Because what most of us have built aren’t knowledge management systems they’re spider-webbed libraries of unprocessed information, equal parts potential insight and documented laziness. A graveyard where good ideas go to be embalmed, tagged, and forgotten.
The mass-media hype promised augmentation. What it delivered was outsourcing. And you cannot outsource the one thing that makes you valuable: your ability to think.
There is no app that can think for you. Notion cannot have your ideas. Obsidian cannot make your connections. Roam cannot understand your context. They are not brains. They are tools and only as intelligent as the human wielding them.
The true value was never in building a second brain. It was in the discipline of thinking clearly enough to write your thoughts down. Not capturing information. Not linking nodes. Thinking. The hard, slow, friction-filled work of taking an idea and wrestling it into something that belongs to you.
My system is no longer a second brain. It’s a thought logbook the flight recorder of my journey as a thinker. The tools are my cockpit: designed to respond to my touch, to extend my reach, to provide clean data. But the flight, the navigation, the final decision?
That is, and must always be, mine.
P.S. This entire essay was written in Obsidian, the same tool discussed here. That’s the irony, and also the point. Obsidian is an excellent platform for writing, thinking, and organizing ideas. I have never said anywhere that it is a bad tool. What I’ve learned is that no app, no matter how powerful, can replace the slow and deeply human process of thinking.
A “second brain” is a personal knowledge management (PKM) system where you use digital tools like Obsidian, Notion, or Roam Research to capture, organize, and connect information externally. The concept, popularized by Tiago Forte’s book Building a Second Brain, promises to augment your thinking by offloading memory to a trusted digital system.
The second brain fails for most people because they confuse collecting information with understanding it. The system encourages hoarding notes, quotes, and highlights without requiring the hard cognitive work of processing and synthesizing that information. You end up with a beautifully organized library of other people’s ideas that you never actually use or internalize.
The Collector’s Fallacy is the mistaken belief that amassing information is the same as learning it. It’s the psychological trap of feeling productive because you’re saving articles, highlighting passages, and creating notes when in reality, you’re just moving information from one place to another without building genuine understanding or skill.
No. Obsidian, Notion, Roam, and similar tools aren’t inherently bad. The problem is the metaphor and how people use them. These are powerful tools when used as workshops for thinking rather than warehouses for collecting. The issue is treating them like a “brain” that can think for you, rather than as a notebook that captures your thinking.
Graph views create the illusion of insight through visual pattern-matching. Your brain sees connected nodes and interprets it as a network of understanding, but most auto-linked connections are syntactic (matching words) rather than semantic (meaningful relationships). A note on “stress” in psychology linking to “stress” in aircraft engineering isn’t a real insight it’s just two words that happen to be spelled the same way.
The IKEA Effect is a cognitive bias where we overvalue things we’ve built ourselves. In PKM systems, this means the more time you spend creating elaborate organizational structures, custom templates, and complex workflows, the more convinced you become that the system is valuable even if it’s not actually helping you learn or think better.