Monday, 8:47 a.m.
Seven Slack DMs you haven't opened. Three 1:1s stacked before lunch. A half-written planning doc from Friday. A decisi...
For further actions, you may consider blocking this person and/or reporting abuse
The 'brain is a terrible database' line is a hard truth. I’m currently mid-build on Commerza (a framework-less ecommerce engine), and I learned this the expensive way.
I hit a major refactoring disaster recently where I lost 40% of my backend logic. What actually saved the project wasn't just my code backups, but the fact that I had documented my 'security primitives' (SQL transactions, auth logic, etc.) separately. It turned a total loss into a 9-hour reconstruction job instead of a 1-month failure. I’m definitely looking into the PARA folder structure for my next project to keep those architecture decisions even more accessible.
Solid approach, love the mix with Obsidian and GDrive
Yes this is applicable for any usecase not just managers but also engineers / builders.
This is similar to my own! I've recently added hooks and started logging the conversation back and fourth and I inject memories using hooks and a vector db (if I have memory mode on) into the prompt itself. I have ADHD and memory issues, so I like to be reminded of what happened in the past, but it actually seems to improve a lot of answers since so much of what I discuss with AI is related.
I did add a scripts and journal folder, both for work and both shared with other projects. I have a wiki folder, too, where all the processed files live. That's a pretty big strike against the methodology, but I think it's important that we all change the system to fit our own needs. My wiki folder is the same information found in other areas, just written from a different, technical perspective vs a lot of opinion and emotion found elsewhere. That's how it's broken up in my head, so that's how it's broken up in my second brain.
Where can I see all of the steps to configure the shared brain? Do I need paid subscription with Claude?
based on the look of it wou'll need a Max or at least a Pro plan
Mine requires the smaller of the two max plans, and it's pretty similar. This doesn't require top models for everything, though. A lot of processing can be done with haiku if you write tight enough prompts, but that's not always easy when exploring new concepts.
My first version of this used opus to write the prompts and md files, and haiku to actually execute those prompts. Then had sonnet fix things along the way. I used regular Claude app for the design phase, Claude Code for the rest. I don't have the best frame of reference (I'm spoiled), but I think that would have worked with Pro usage levels.
Not great but still like the tool and how it works.
This all originated (the fad, not the concept) with a tweet by Andaarej Karpathy, a respected voice in the AI space. This is the main gist of his setup, which is pretty much what's being described in the post above.
Since this post, there have been a BUNCH of youtube videos and internet tutorials. Best bet is searching "Obsidian Second Brain" and finding a resource that speaks to you personally. It does require a subscription, but it ranges in usage depending on how often you use it and how you use it. I use mine for everything, coding included, so I need a Max subscription, but someone using it occasionally might only need a Pro subscription. It'd be really tough on a free subscription.
I have done something similar for my personal project tracking.
This is really good idea I have been thinking how to organize all my vibe coding ideas.
Yes this is applicable for any usecase not just managers but also engineers / builders.
The "brain as terrible database" framing is a great reframe. The adjacent problem I keep running into: most second-brain systems are great at write and terrible at recall. I've had the most luck with a flat daily-notes markdown tree + grep + a small semantic search layer on top — the structure stays dumb enough that tools (and agents) can read it, but retrieval still works because of embeddings. Heavy folder hierarchies tend to become the place notes go to die.
i've been using a physical notebook for morning dumps and it's wild how much it reduces that mental cache pressure. no notifications no context switching. feels like defragging my brain before the day even starts