DEV Community

Chris
Chris

Posted on

Why Every Developer Needs a Second Brain

#obsidian #productivity #devtools #webdev

Your notes belong to you... not a SaaS company's database. Obsidian is a markdown-native infinitely extensible tool where you can build what developer's dub a "second brain".

Contents

Free, local, and actually yours

Obsidian is free for personal use. Your vault is just a folder of .md files on your machine. There's no proprietary format, no subscription required, no max and no limits.

The "cloud" is growing, and our farmland is being replaced with data centers. I have iCloud which helps with my phone backup and makes it easy to setup new devices, but aside from that, I don't want my data on someone else's machine. It's inevitable on some level, but I like to do what I can to prevent it.

I digress... for your Obsidian notes, you can back them up with git, sync with your own solution, or keep them entirely offline. You can get an Obsidian Sync subscription - more on that next - but the free version is:

  • ✅ Free for personal use
  • ✅ Plain markdown files — open in any editor
  • ✅ Privacy-first, completely offline
  • ✅ No account = No limits
  • ✅ No polluting the ever growing "cloud"

Password protection and end-to-end encryption

You can set a vault password to lock access to your notes at the app level if you wanted added security.

If you use Obsidian Sync, your data is encrypted end-to-end before it ever leaves your device. Sync keys never reach Obsidian's servers. Even if their infrastructure were compromised, your notes are unreadable.

💡 Note on Sync: Obsidian Sync is the paid cloud option, but it's entirely optional. Many devs use iCloud, Syncthing, or a private Git repo instead — and keep E2E encryption handled on their own terms.

Obsidian Bases ✨ EXCITING NEW FEATURE!!

Think Notion databases — but in your local markdown vault. And of course, it's local-first - All data stays in your vault as plain markdown and not in an external DB.

Bases lets you create structured views over your notes using a simple table or gallery interface. Filter, sort, and group notes by properties without leaving Obsidian. For developers this means you can finally treat your vault like a lightweight database, with zero sync overhead.


Screenshot from www.nickgracilla.com

Feature What it does
Table view Spreadsheet-style view over frontmatter properties across notes
Filter & sort Query notes by any property - tags, date, custom fields
Gallery view Card-based visual layout for overviews and kanban-style boards

Coding Funsies

Add blocks of code IN your notes:

Use the Code Emitter plugin inside your vault turning Obsidian into a lightweight programming environment - great for documenting scripts, learning new languages, and you could even use it for prototyping.

You'll even get errors!

Once you have your code block, you can use the Copy Inline Code icon to simply click to copy.

Custom CSS: full control over print and PDF export

Obsidian supports custom CSS snippets! Drop a .css file in .obsidian/snippets/ and it applies vault-wide.

I just had killer use case for this when I wanted to control my PDF exports, because boy - they were ugly! I grew tired of typing "sorry for the formatting, it's from my Obsidian notes" every time I shared a document with someone.

/* .obsidian/snippets/print-control.css */

@media print {
  .sidebar,
  .status-bar { display: none; }

  .markdown-preview-view {
    font-size: 11pt;
    max-width: 100%;
    padding: 0;
  }

  h1, h2, h3 {
    page-break-after: avoid;
  }

  pre, code {
    white-space: pre-wrap;
    border: 1px solid #ccc;
  }
}
Enter fullscreen mode Exit fullscreen mode

Use this to strip chrome, set print-friendly typography, control page breaks around headings and code blocks, and produce clean PDFs from technical notes without touching a separate tool. Can you imagine copying some to or from oldschool Word? The absolute horror!

💡 Pro tip: Combine a print snippet with a dedicated export theme (a separate CSS snippet you toggle only before printing) for perfectly formatted technical docs every time.

Supercharge your vault with Claude + MCP

Obsidian has a community plugin called Local REST API that exposes your vault over HTTP — and that's all you need to connect it to AI.

What you need

Wiring it up

In your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "obsidian": {
      "command": "npx",
      "args": ["-y", "mcp-obsidian"],
      "env": {
        "OBSIDIAN_API_KEY": "your-api-key-here",
        "OBSIDIAN_HOST": "http://127.0.0.1:27123"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

In your Claude Code VS Code config (.claude/settings.json):

{
  "mcpServers": {
    "obsidian": {
      "command": "npx",
      "args": ["-y", "mcp-obsidian"],
      "env": {
        "OBSIDIAN_API_KEY": "your-api-key-here",
        "OBSIDIAN_HOST": "http://127.0.0.1:27123"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Your API key is generated inside the Local REST API plugin settings in Obsidian.

What you can do once connected

  • Ask Claude to search, read, and write notes in your vault
  • Have Claude append meeting summaries or code snippets directly to existing notes
  • Use Claude Code to reference your vault docs while you're coding — without copy-pasting anything

💡 Pro tip: Keep a CLAUDE.md file in your vault root as a persistent context file — Claude will read it automatically and know your preferences, project structure, and shorthand without you repeating yourself every session.

What Obsidian plugins are you using that belong on this list? Drop them in the comments.

Links to Get Started

Obsidian

Plugins

Claude / AI

Referenced

Top comments (0)