CourseAI NewsGuidesGitHubAboutTake the pill
Course/How to Talk to It

9 min · +120 XP

Where Everyone Stalls (and the 10-Second Fixes)

The six moments beginners think they're stuck. They're not.

By the end of this lesson

You'll recognize every 'uh oh' moment in advance — and know the one-line fix.

Almost nobody quits because building is hard. They quit at one of seven tiny moments that LOOK like dead ends but have ten-second fixes. Read these once and you're immune.

The seven moments

  1. 1“It asked me a technical question I don't understand.” → Reply exactly this: 'decide yourself and keep going'. That's a complete, correct answer. (Or run the skip-permissions mode and it won't ask at all.)
  2. 2“It's been working for several minutes. Did it freeze?” → No — it's building. Lines scrolling means work happening. Let it finish; long silence + no lines for a very long time is the only time to nudge it: just press Enter and ask 'how's it going?'
  3. 3“The result isn't what I imagined.” → Don't start over. Say what's wrong like you would to a person: 'too dark, make the buttons bigger, the chart should be weekly'. Iterating IS the workflow, not a failure.
  4. 4“It's going in the wrong direction mid-build.” → Press Esc — it politely stops. Then redirect: 'stop, instead do X'. You're the director; interrupting is allowed.
  5. 5“A red error appeared.” → Copy it, paste it to Claude, say 'fix it'. That's the entire skill of debugging now.
  6. 6“I closed the terminal. Is everything gone?!” → Nothing is gone. Your files are on the computer, in your project folder. (One nuance: if your tool lived at a localhost address, the PAGE stops answering when the terminal closes — the files and your data stay; Module 6 shows the ten-second restart.) Getting back takes ten seconds — next block.
  7. 7“It says I've hit my usage limit and must wait.” → Normal, not a scam: your plan's budget refills every few hours (very heavy weeks can also bump a weekly cap — same answer). Take the break or upgrade. (Also a reason to send one complete request instead of twenty small ones — drip-feeding burns budget faster.)
Coming back to a project — the command nobody tells beginners
claude --continue

Open the terminal IN your project folder — Mac: right-click the folder → New Terminal at Folder; Windows: open the folder, Shift+right-click an empty spot → 'Open in Terminal' — and run this: it reopens your LAST conversation in that folder with all its memory of the project. Plain claude starts a fresh chat — also fine, just tell it 'continue working on the project in this folder' and it reads the files and picks up.

✓The meta-rule

Whenever you feel stuck, type the feeling itself into Claude: 'I don't understand what just happened, explain simply and tell me what to do next.' It's your guide, not just your builder. There is no stuck — only unasked questions.

Quick check

You closed the terminal mid-project. What's true?

EAEvgeny Arsentyev

Author

Evgeny Arsentyev

PhD · Chief Product Officer at a healthtech company