Simple explanation
Welcome to Day 6. At some point this week you probably saw a red error message and felt a moment of panic. Today that panic ends permanently. The truth about error messages Error messages are not telling you that everything is broken. They are telling you exactly what went wrong and where. The problem is they are written for developers who understand technical language. For everyone else they look like a wall of red text that means nothing. But here is the secret: you do not need to understand the error. You just need to find the right part of it. The anatomy of an error message Every error message has three parts: 1. The location — which file and which line the problem is on. Usually looks like: src/pages/contact.js line 24 2. The error type — a short label of what kind of problem it is. Usually looks like: TypeError or SyntaxError or Cannot read property 3. The detail — a description of the specific problem. Usually the most readable line in the whole message. You only need the last two lines of the error. The actual error is almost always there. Everything above those last two lines is the trail that led to the error — not the error itself.
What to do
What to do with an error 1. Do not close anything. Do not start clicking randomly. 2. Scroll to the bottom of the red text. Find the last two lines. 3. Copy those two lines. 4. Go to Claude Code and type exactly this: "I got this error. Please fix it: [paste the last two lines here]" 5. Let Claude Code fix it. That is the entire process. You do not need to understand the error. You need to copy the right part and hand it to the right tool. The three most common errors non-developers see "Cannot find module" — something is not installed. Claude Code will install it. "is not defined" — a word was used before it was set up. Claude Code will fix the order. "Unexpected token" — a small typo in the code. Usually a missing comma or bracket. Claude Code will find it in seconds. None of these are serious. All of them are fixable in under a minute with Claude Code. Today's practical task 1. Open your project in Claude Code. 2. Ask Claude Code to deliberately introduce a small error into one file. 3. Watch the error appear. 4. Practise finding the last two lines. 5. Copy them and ask Claude Code to fix it. 6. Watch it fix in seconds. You just broke something on purpose and fixed it. That is a huge confidence shift.
Copy-paste prompt
I got this error. Please fix it and explain in one sentence what caused it: [paste the last two lines of your error message here]
Course note
Key takeaway
Scroll to the bottom of the error. Copy the last two lines. Paste them into Claude Code with "I got this error. Please fix it." That is the entire process — every time.