Building a Second Brain with Dendron

A project-first “second brain” setup can stay organized without constant folder shuffling by using Dendron’s flat-file system and the PARA method’s four buckets: Projects, Areas, Reference, and Archive. The core idea is to capture notes where they’re useful for the work at hand, then automatically “move” knowledge down the hierarchy as it becomes reusable—so active work stays clean while finished research doesn’t get lost.

The transcript draws a sharp line between two note-taking philosophies. Smart Notes is bottom-up and knowledge-structure driven: it’s designed for building expertise over time when the eventual projects are unclear. PARA flips that by starting with known, project-centric goals. Notes are collected around an outcome while the project is active, then reorganized after the work is done. That distinction matters because many people already know what they’re building next and need a system that supports execution, not long-term academic scaffolding.

In Visual Studio Code, the workflow uses the Dendron extension (“dendrine” in the narration) to implement PARA. Unlike systems that rely on folders, Dendron organizes notes through filenames: each note name begins with a prefix (p, a, r, etc.) that corresponds to PARA categories, and periods in the name create hierarchy. The result is a “flat” underlying file structure that still appears nested in the editor. That design makes refactoring practical: changing a note’s name can relocate it to a different PARA bucket without dragging files around—an important quality-of-life feature for people who hate manual reorganization.

The walkthrough uses a real example: a “notary github action” project. While working, the user treats the project folder as a digital workbench, dumping high-level context, subtasks, reminders, and technical stack notes. During the project, research “spikes” produce links and learning notes; once the immediate need ends, those notes get moved into Reference. The transcript emphasizes that Dendron’s refactor command can rename and relocate entire note hierarchies at once, avoiding tedious tag updates or manual file moves.

After Projects, the system moves into Areas—ongoing responsibilities like a “cloud advocate” role, plus other continuing threads such as writing or family. Notes that remain relevant across time shift into Areas when they support recurring responsibilities rather than one-off deliverables. Reference holds reusable snippets and outputs discovered during automation work (for example, Terraform snippets used multiple times). Archive is the long tail: retrieval frequency drops as notes descend the hierarchy, so archived material is revisited rarely.

Finally, the transcript notes that this PARA + Dendron approach can be implemented beyond VS Code and markdown tools, even in minimalist setups like plain text or Apple Notes. It also mentions Dendron features like journal entries and meeting templates, while keeping the focus on PARA’s movement of knowledge through Projects → Areas → Reference → Archive.