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.
I fell right into the YouTube rabbit hole of “build your second brain with me.” At the time, it made perfect sense. I was balancing psychology studies, cadet pilot training, and blogging. Between research papers, aerodynamic principles, and half-finished article ideas, my head was overflowing. The promise of a “second brain” felt like salvation one system to hold it all, connect the dots, and hand me insights on demand.
So I went all in. I spent hours tweaking dashboards, fine-tuning tagging systems, and clipping quotes and highlights into Obsidian. My vault grew fast. It looked professional, even a little intimidating. Opening it gave me this rush like, wow, I’ve built something powerful.
But looking back, I can see what was really happening. That feeling wasn’t insight. It wasn’t learning. It was me getting high on effort justification, the psychology bias where the harder we work on something, the more valuable it feels, even if it’s not actually helping. The system felt smart because I poured so many hours into it.
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.
Little did I know I was constructing a beautiful cage for my own curiosity, and soon enough, I was staring at the graph view like a patient staring at their MRI scan, seeing everything and understanding nothing
The Psychology of the Build
My first months with a “second brain” weren’t about learning at all. They were about psychological biases disguised as productivity. I wasn’t building a brain; I was building a monument to my own cognitive wiring.
The IKEA Effect (Effort Justification): Because I’d spent hours perfecting templates, tagging systems, and color codes, the vault felt valuable it had to be. The more I tinkered, the more indispensable it seemed. Critiquing the system felt like critiquing myself.
Cognitive Offloading & The Zeigarnik Effect: Writing something down gave instant relief. Psychology tells us that unfinished tasks create tension; capturing them tricks the brain into feeling complete. Each highlight, quote, or idea dumped into Obsidian felt like learning. But I was clearing my mental desk by filing things away instead of processing them.
The Collector’s Fallacy: Soon I had hundreds of notes: Piaget’s stages, Bernoulli’s principle, scattered marketing insights. I looked busy, but I wasn’t thinking. I was hoarding. A dragon sitting on shiny gold it would never spend.
Productivity Theater: Many nights I’d “study” for three hours, but half that time went into reformatting notes, fixing headers, or linking files. It looked like work; it even felt like work, but it was performance. Stage props instead of substance.
And honestly, that was the trap. I thought I was building a tool to free my mind. What I actually built was a very tidy cage for my thoughts.
The Cracks in the Foundation: Where the Metaphor Breaks Down
After the euphoria faded, a low-grade, cheap frustration started to emerge. The system wasn’t doing anything. No insights were emerging. I felt like a scammer scamming myself. 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 the evolution and the human biology of the brain. I treated it as a hard drive, and my notes app was a perfect external backup. As if someday my brain will be corrupted and I will have my notes app as the eternal backup of my knowledge.
But the brain isn’t static, right? It‘s reconstructive and dynamic. The memory isn’t a stored fact. Memory is kinda like the brain remembering the last time it recalled the chain of events, a separate episodic trace.
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 would never learn to walk on my own.
2. Apophenia & The Illusion of Insight: Obsidian has this beautiful, foolish feature called Auto-linking. Us mere mortals link with context and semantically. It links based on text, not context. Emotional stress and aircraft airframe stress are the same thing for it. Like a kid who every time sees a brown rectangle and calls it a chocolate.
My pattern-seeking brain (what in psychology we call apophenia) would light up with excitement. “I’ve found a connection!” it would cheer. But in reality, there was nothing smart about the system at all. It didn’t “know” that one thing was a state of mind and the other a physical force.
It was just lining up similar-looking words. I was the one assigning meaning to it turning a mechanical matching of symbols into a moment of supposed insight. In truth, I wasn’t discovering anything new. I was just watching a coincidence and convincing myself it mattered.
3. Cognitive and maintenance overload: the same system that was meant to reduce my cognitive load became the primary source of my cognitive load. The first 100 notes are fun. The next 400 are a nightmare. I’d create a tag called #psychology/cognitive-bias, only to later decide #cognition/bias was a better structure. I’d spend entire sessions “refactoring” my vault, retagging, relinking, and reorganizing instead of engaging with new ideas. The tool meant to free my mind had become its most demanding taskmaster.
The turning point from storing to logging
The shift happened slowly, yet suddenly. I was preparing for my technical general exam, which involved writing and researching for a blog.
I had all the ingredients: notes on the Yerkes-Dodson 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.
In frustration i did something stupid; I closed all my notes and made a new vault, started from scratch and wrote notes. 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.
Looking back, it was the best decision I had ever made.
In that moment i stopped archiving and started logging. 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
“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
This new approach transformed my tools from static repositories into dynamic workshops. But the future promises an even more profound shift: the move from a tool to a partner.
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.”
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 journey through the hype cycle of Build your ”Second Brain” was frustrating yet insightful and led me to a bitter truth. The entire metaphor is a big fat lie.
Not an oversimplification. Not an imperfect analogy or a bad interpretation by me. A lie.
You don’t have a second brain. You have a primary brain which thinks, processes, and a filing cabinet where curiosity goes to die.
Calling it “Brain” was a clever marketing strategy and excellent framing to sell note-taking apps, courses, and templates. It’s nothing but 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 isn’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.