Note-Taking in Markdown: Methods and Workflows

The best note-taking system is one you'll actually use. This guide compares the most popular methods and shows how to implement each in markdown.

Method 1: Zettelkasten (Linked Notes)

Each note contains one idea. Notes link to each other to form a web of knowledge.

Core principle: Notes have value not just in isolation, but in their connections.

markdown
---
id: 20260105143200
title: Immutable data structures
tags: [programming, data]
---

# Immutable Data Structures

Immutable data structures cannot be modified after creation.

**Why this matters:** Eliminates a class of concurrency bugs related to shared mutable state.

**Trade-offs:** Memory overhead of copying — mitigated by structural sharing.

**See also:**
- [Pure functions](./20260101120000.md)
- [React's useState mental model](./20260103092100.md)

Best for: Researchers and writers building a long-term personal knowledge base.

Method 2: Cornell Notes

Splits each note into cues (left), notes (right), and a summary (bottom). Originally designed for lecture notes.

markdown
# Lecture: Distributed Systems — CAP Theorem
**Date:** 2026-01-05

## Cues | Notes
--- | ---
What is CAP? | A distributed system guarantees at most 2 of: Consistency, Availability, Partition tolerance
Why not all 3? | Network partitions are inevitable. During one, choose C or A.
CP vs AP? | CP: banking (consistency). AP: DNS, shopping carts (availability).

## Summary
The CAP theorem forces a design choice during network partitions. Most systems choose AP with eventual consistency.

Best for: Students, structured learning from books or videos.

Method 3: GTD (Getting Things Done)

markdown
# Inbox (capture everything here)
- [ ] Look into rehype-slug for blog TOC
- [ ] Reply to Sarah's PR review

# Projects

## Launch blog redesign
- [ ] Write 5 new articles
- [x] Update homepage hero

# Waiting For
- [ ] Design review from Priya (sent 2026-01-03)

# Someday / Maybe
- Learn Rust
- Read *A Philosophy of Software Design*

Best for: Anyone managing many projects, or who feels overwhelmed by their to-do list.

Method 4: Evergreen Notes

Notes are written to be refined over time — not fleeting captures, but durable named concepts.

Rules:

1. Titles are complete sentences: "Habits compound over years" not "Habits"
2. Write for your future self — assume you'll have forgotten the context
3. Link freely, file loosely

markdown
# Premature optimization is the root of most performance bugs

We optimize before measuring because it feels productive. But unmeasured optimization often targets the wrong bottleneck, and optimized code is harder to change.

**Corollary:** Profile first, then optimize the one thing that matters.

See also: [[Measure before optimizing]], [[Big-O is not the only cost]]

Best for: People who write a lot and want notes that get more valuable over time.

Choosing Your Method

Recommendation: Start with daily notes for two weeks. See what recurs. That's where to build structure.

The One Rule That Matters

Capture now, organize later. A note taken imperfectly beats a note not taken at all.

Open MarkGenie, paste in one idea you had today, and that's your note-taking system started.