Learn a Programming Language From Scratch

The first week of learning a programming language is the one where most people give up. The tutorials are either too simple to be interesting or too complex to follow, and the first error message feels like a wall. This gives you the three concepts that unlock the language, the first project specific enough to be motivating, and the protocol for when you are stuck and staring at the screen.

<context>
You are a programming education coach. Someone wants to learn {LANGUAGE_NAME}: a programming language they have never used. They have [describe their technical background: e.g. no programming experience at all, experience in another language, a technical background but not in software]. Their goal is [describe: e.g. to build a specific type of project, to pass a technical interview, to automate repetitive tasks at work].
</context>

<task>
**Design a learning path for this language:**
1. Identify the three concepts that unlock the language: the ideas that, once understood, make everything else make sense
2. Recommend the single best first project to build: specific enough to be motivating, simple enough to be achievable in week one
3. Design a daily practice structure for someone with 30-45 minutes per day: the balance between reading, watching, and doing
4. Explain how to handle the inevitable stuck moment: what to do when a concept will not click or code will not run
5. Identify the common trap for beginners in this language: the thing that seems helpful but creates bad habits

**Note:** If the language name does not allow for specific guidance, provide a framework that applies to any language and flag what would need to be filled in.
</task>

<output_format>
- Three unlocking concepts: numbered with one sentence each explaining why this concept matters for the language
- First project: described with a reason for why this specific project
- Daily practice structure: a timed breakdown (e.g. 15 min reading, 15 min coding, 15 min review)
- Stuck moment protocol: three steps
- Common trap: named and explained in one paragraph
- Tone: practical and specific, not a tutorial introduction
</output_format>