Chapter 5: Errors Are Normal (Here's What to Do)

One-line summary: Something will break. That's fine. Here's exactly how to fix it without stress.

---

#First: Take a Breath

Things will go wrong. Pages will be blank. Buttons won't work. Red text will appear that makes no sense.

This is not a sign that you did something wrong. This is not a sign that you're bad at this. This happens to professional developers who have been coding for 20 years. It just happens.

The only difference between a beginner and a pro? The pro knows how to fix it. And now, so will you.

---

#The #1 Rule: Paste the Error to Bob

Don't try to figure it out yourself. Don't try to describe it in your own words. Don't guess.

Just copy the error and paste it to Bob. The whole thing.

Bob reads errors the way you read text messages — instantly and completely. He'll tell you exactly what it means and fix it. Error messages look scary to humans but they're basically instructions for Bob.

---

#How to Find the Error

If the page looks broken or is blank:

1. Press Ctrl + Shift + J on Windows, or Cmd + Option + J on Mac
2. A panel opens — this is the browser console (think of it as the app's diary of what went wrong)
3. Look for red text
4. Copy all of it
5. Paste it to Bob

If Bob told you something failed while building:

Scroll up in the Claude Code session to where it went wrong. Copy the red/error text you see. Paste it back.

---

#Common Situations and What to Say

"The page is completely blank" Open the browser console (Ctrl+Shift+J), copy any red text, and tell Bob:

"The page is blank. Here's what I see in the console: [paste the red text]"

"It says compilation failed" Copy the full error message from Bob's output and say:

"I got this error when building: [paste the whole thing]"

"The button doesn't do anything when I click it"

"When I click the Donate button, nothing happens. I checked the console and there's no error. It just doesn't respond."

"It looks broken on my phone"

"The layout looks messed up on mobile. The buttons overlap and the text goes off-screen."

"I don't understand what went wrong"

"Something broke and I'm not sure what. Can you look at the current state and tell me what's wrong?"

---

#The Nuclear Option

Sometimes things get tangled and it's easier to start fresh on one piece. That's completely valid.

Just say:

"Bob, this feature isn't working and we've gone in circles. Let's scrap just this part and rebuild it from scratch."

You don't have to throw out everything — just the broken piece. Bob will rebuild that part clean.

---

#The Patience Mindset

Sometimes a fix takes 2-3 rounds of back-and-forth. That is completely normal.

• Round 1: Bob fixes the obvious issue
• Round 2: That fix reveals a second thing
• Round 3: That's sorted, done

This isn't Bob failing. This is just how building works, for everyone, always. The difference is that with Bob, those 3 rounds take 10 minutes instead of 3 days.

You're going faster than any developer could by hand. Trust the process.

---

Next up: Making the app feel like yours with custom branding and design. →