Learning

---
name: learning
description: Fast-learning techniques tuned for ADHD brains — the 3-phase Skim/Do/Explain method, active recall, spaced repetition, and chunking overwhelming material into small steps. Use when the user is starting a new topic or technology, feels overwhelmed by material, is struggling to retain information, or asks for a study system. Not a formal pedagogy or certification-prep guide.
---

# Skill: Learning

> **Purpose**: Learn faster and retain more, especially with an ADHD brain.

## When to Use
- Starting a new topic or technology
- Struggling to retain information
- Feeling overwhelmed by material
- Needing a study system

---

## Fast Learning System

### The 3-Phase Method

**Phase 1: Skim (10 min)**
- Read headings, bold text, and code examples only
- Goal: Get the shape of the topic, not details
- Output: Write 3 bullet points of what you think it's about

**Phase 2: Do (30 min)**
- Build something small with the new concept
- Don't read docs line-by-line — search for what you need
- Goal: Working code, even if ugly

**Phase 3: Explain (10 min)**
- Write a 3-sentence explanation as if teaching a beginner
- If you can't explain it simply, go back to Phase 2
- This is where real understanding happens

---

## ADHD-Friendly Techniques

### 1. The Pomodoro Micro-Sprint
- **15 minutes** of focused work (not 25 — shorter is more ADHD-friendly)
- **5 minute** break (stand up, move)
- After 3 sprints, take a 15-minute break
- Use a physical timer or phone timer — not a browser tab

### 2. Start With the Fun Part
Don't force yourself to read docs first. Start coding, hit a wall, then read the specific doc you need. Curiosity-driven learning sticks better.

### 3. One Tab Rule
Close everything except:
- Your editor
- One documentation tab
- Your terminal

More tabs = more distraction = less learning.

### 4. Body Doubling
Work alongside someone (physically or virtually). Just having someone nearby increases focus. Use study streams or coworking sessions.

### 5. Externalize Everything
Your brain is for processing, not storage.
- Write TODO lists on paper
- Use sticky notes for current task
- Keep a "parking lot" file for random ideas that pop up

---

## Retention Strategies

### Active Recall
Don't re-read. Test yourself.

```
After learning about closures:
1. Close the docs
2. Write: "A closure is ___"
3. Write a code example from memory
4. Check against docs
5. Fix mistakes
```

### Spaced Repetition Schedule
| When | What to Do |
|------|-----------|
| Same day | Write a summary from memory |
| Next day | Rebuild the code example without looking |
| Day 3 | Explain it to someone (or write it as a doc) |
| Day 7 | Use it in a real project |
| Day 30 | Review and refactor old code using this concept |

### Teach It
The fastest way to learn anything:
1. Learn the concept
2. Build something with it
3. Write a short guide explaining it
4. The gaps in your guide = gaps in your understanding

---

## When You're Stuck

### The 15-Minute Rule
1. Struggle with it for 15 minutes (set a timer)
2. If stuck after 15 min, ask for help (AI, colleague, Stack Overflow)
3. When you get the answer, write down WHY you were stuck

### Unstuck Checklist
- [ ] Did I read the full error message?
- [ ] Did I Google the exact error message?
- [ ] Did I check if my code actually saved/compiled?
- [ ] Did I try the simplest possible version?
- [ ] Did I take a 5-minute break?

---

## Building a Learning Habit

### Daily Minimum
Set an absurdly small daily goal:
- ❌ "Study Java for 2 hours" → too big, you'll skip it
- ✅ "Write 1 Java method" → small enough to always do

### Streak System
Track consecutive days. Never break the chain for more than 1 day. 
- Day 1-7: Building the habit
- Day 8-21: It gets easier
- Day 22+: It feels wrong NOT to do it

---

## Best Practices
1. **Learn by doing** — reading alone doesn't work
2. **Smaller chunks** — 15 min focused > 2 hours distracted
3. **Test yourself** — active recall beats re-reading 10x
4. **Write it down** — externalize to free up mental RAM
5. **Forgive yourself** — missed a day? Start again tomorrow, not next week

## Common Mistakes
| Mistake | Fix |
|---------|-----|
| Tutorial hell (watching without coding) | Code along, then rebuild without the tutorial |
| Trying to learn everything at once | Pick ONE concept, master it, move on |
| Studying when exhausted | Learn during peak energy hours |
| No practice after learning | Use it in a project within 48 hours |
| Comparing your speed to others | You're competing with yesterday's you |