Developers ask more of a notes app than most people do: markdown that renders the way you typed it, code snippets that stay monospaced and don't get "helpfully" reformatted, and links between notes so a debugging log connects to the runbook it came from. Plain text you own forever is the baseline, not a bonus. We make one of the apps below, so here's the honest shortlist — and the honest place where our own app isn't the pick.
What a developer actually needs
- Real markdown, not a lookalike. Fenced code blocks (```), inline
code, tables, and headings — stored as plain.mdyou cangrep, diff, and commit. WYSIWYG editors that approximate markdown will bite you the first time you paste a shell command. - Code snippets that behave. Monospace, no smart-quote substitution, no autocorrect turning
--flaginto an em dash. Syntax highlighting is nice; not mangling your paste is essential. - Linking between notes. The Zettelkasten payoff applies directly to engineering knowledge — an error message links to its fix, an atomic note on a pattern links everywhere you used it.
- An exit. If you can't
git-back it or export cleanly, you don't own it. Lock-in is technical debt.
The shortlist
| Your situation | Start with | Why |
|---|---|---|
Local-first, plain .md, wikilinks, git-backed |
Obsidian | The developer default — a folder of markdown files with a graph and a huge plugin ecosystem. How it stacks up vs Notion |
| Team docs, runbooks, and a shared engineering wiki | Notion | Databases, shared pages, and code blocks in a workspace — best when other people need to read it |
| Fast personal capture on iPhone, offline, ask across your own notes | Clair Mind | One-tap capture of the 2am insight, works offline, exports to Markdown, and answers questions across what you wrote |
| Zero-config plain text, own your files forever | A files-based markdown app | Just text files and a folder — nothing to break, nothing to leave |
Where each one earns it
Obsidian is the honest answer for most developers. It's markdown all the way down, the files sit in a folder you can put under version control, and backlinks turn scattered notes into a real knowledge graph. The cost is that you assemble your own setup — it's a workbench, not an appliance.
Notion wins the moment the notes stop being yours and start being the team's. Runbooks, onboarding docs, an architecture wiki — that's its home turf. As a personal scratchpad it's heavier than it needs to be, and its "markdown" is a rendering of a database, not files you own.
Clair Mind — our app — is deliberately narrow, so here's the honest boundary. It's built for capturing before the thought fades on your phone and asking your notes in plain language later, all offline and private. It is genuinely good for the ideas you have away from the keyboard. It is not a code editor, it has no syntax highlighting, and it's iPhone-first — so it's a companion to your real dev notes, not a replacement for a git-backed vault. If your notes are 80% code, reach for Obsidian.
The method still beats the tool
Whatever you pick, the habit does the work. Keep engineering notes atomic — one idea, one fix, one gotcha per note — so they link cleanly and resurface when the same bug returns. A good capture habit and a maintainable structure matter more than which app renders your code fences. The best notes app for developers is the one you'll actually open mid-incident, in your own words, that hands your notes back when you're done with it.