dx-patterns

# Developer Experience (DX) Patterns

Build tools and systems that feel natural, reduce friction, and let developers reach flow state. Grounded in research and battle-tested in production.

## The DX Framework

Based on research by Greiler, Storey, and Noda, the **DX Framework** defines developer experience through three pillars:

### 1️⃣ Feedback Loops

**Definition:** How quickly developers know if something worked or failed.

**Good Feedback:**
- Tests run fast (< 5s for unit tests)
- Errors appear immediately (pre-commit hooks)
- Success is obvious (green checkmarks, clear output)
- Failures include actionable suggestions

**Bad Feedback:**
- Tests take 30s to run
- Errors appear only after CI fails
- Stack traces with no context
- "Something went wrong" with no solution

### 2️⃣ Cognitive Load

**Definition:** How much mental energy developers spend understanding your system.

**Reduce Cognitive Load:**
- Consistent patterns (same patterns everywhere)
- Clear naming (unambiguous function/variable names)
- Progressive disclosure (novice → expert paths)
- Visual hierarchy (important things stand out)
- Documentation that answers "why" not just "how"

**Increase Cognitive Load:**
- Hidden magic (implicit behavior)
- Inconsistent patterns (each tool different)
- Cryptic names (short abbreviations)
- Everything visible at once (no hierarchy)
- No documentation

### 3️⃣ Flow State

**Definition:** Developers' ability to maintain deep focus and productivity.

**Enable Flow:**
- Minimize context switching (related files nearby)
- Remove blockers (dependencies available)
- Clear next steps (obvious what to do)
- Intrinsic motivation (meaningful work)
- Mastery progression (skill growth visible)

**Block Flow:**
- Constant interruptions
- Broken dependencies
- Unclear requirements
- Busywork with no purpose
- No sense of progress

---

## DX Patterns in Practice

### Pattern 1: Progressive Disclosure

Show complexity gradually, not all at once.

#### ❌ Bad: Everything Vi