## User Profile (Stable Preferences)

These preferences apply to all learning plans for this user:

### Learning Style - Strong Preferences

1. **"Designed for ~1 hour per day"** - Prefer smaller daily learning routine rather than long learning blocks on weekends

2. **"Prescriptive, canonical paths"** - One well-documented learning path per learning concept. I find choice and options within learning content to be distract from my learning objective.

3. **"High signal-to-noise ratio, theory-first"** - I learn well from reading documentation and extracting concepts. I don't need hands-on work for everything. Respect my time by being efficient and focused.

4. **"Content scoped to my learning goal"** - Identify the subset of each learning resource that is in the critical path of my learning objective. Tell me when I can skip portions of learning content. This includes hands-on exercises; if a resource includes labs or projects, tell me whether I need to do them or skip them.

4. **"Concise explanations without excessive caveats"** - Learning content must focus on explaining the core concept clearly. One-sentence acknowledgment of exceptions/variations is sufficient. Don't clutter content with defensive explanations about edge cases that aren't relevant to understanding fundamentals.

### Learning Style - Conditional Preference

5. **"If hands-on work is included, it must be well-integrated:"**
   - Clear, prescriptive setup (specific hardware/software with links to obtain/purchase, clear installation steps)
   - Clear value proposition (why this exercise teaches the concept better than reading)
   - Comprehensive mapping (exercises should apply all recently-taught concepts, not a sparse subset)
   - Verification mechanisms (automated tests, expected outputs, or other immediate feedback)
   - If these criteria aren't met, I prefer pure documentation/theory resources instead

### Learning Style - Nice to have

6. **"Visual/animated content when available"** - I prefer video format but not required when other factors are strong.

7. **"Dense reference materials are okay for reference"** - Datasheets, manuals, etc. are acceptable as reference, not primary learning. Dense materials are good for helping me translate concepts I have learned to my specific learning objective (for example, if I learn MIPS assembly through excellent interactive content, but then need to read a datasheet to translate those concepts to dsPIC assembly)

---

### Negative Example (What NOT to recommend)

**Mike Silva's "Introduction to Microcontrollers" series** exemplifies several anti-patterns for my learning style:

- **Low signal-to-noise ratio**: Spent 6-10 hours to extract ~1 hour of useful concepts. Too much content written defensively for expert critics rather than to teach beginners efficiently.

- **Multi-paradigm without clear purpose**: Showed every code example in both AVR and ARM assembly, plus C. The ARM examples duplicated AVR insights without adding value. The C examples were off-topic for my goal (learning to read dsPIC assembly).

- **Poorly integrated hands-on work**: Labs were probably unnecessary for this topic and had unclear hardware requirements (no specific product recommendations or links to purchase, unclear if 2013 hardware still available), no setup instructions, unclear value proposition (why blink an LED in C to learn microcontroller concepts?), and sparse concept mapping (taught concepts 1-5, lab only used 2 and 4, leaving "dead knowledge").

- **Choice paralysis**: Offered multiple architecture options (AVR vs ARM vs simulator), conditional equipment advice ("you might want an oscilloscope but don't need it... but if you do get one you'll learn more"), and left decisions to the learner without enough context to evaluate them.

**In contrast:** Nand2tetris Part 1 was an excellent fit—prescriptive toolchain, automated tests for every project, comprehensive concept-to-practice mapping, tight scope (one invented architecture), high efficiency, and hands-on work that had clear value (building understanding through progressive construction).