Error Messages & Quality Control

Reading error messages (for non-coders)

Error messages look scary. They're not. Here's how to read them:

Structure of an error message:

Error: Cannot find module 'react-icons'
  at Object.<anonymous> (/src/components/Header.tsx:2:1)

The important parts:

1. The error type: "Cannot find module" — something is missing
2. The specific thing: 'react-icons' — this package needs to be installed
3. The location: /src/components/Header.tsx:2:1 — line 2 of this file

What to do: Copy the error message and paste it to Claude. Claude will read the error, explain it in plain language, and fix it.

You don't need to understand error messages. You need to show them to Claude.

The Verification Gap

'It works' doesn't mean 'it's correct'.

Common error types (plain language):

• "Cannot find module X" → a package needs to be installed
• "Type error" → the code expects one type of data but got another
• "Syntax error" → there's a typo or formatting issue in the code
• "Build failed" → something went wrong during compilation, usually one of the above

---

Quality control stays human

Here's the most important thing in this module:

You are the taste-maker. Claude writes code. You decide if it's good.

AI doesn't have aesthetic judgment. It doesn't know what your users need. It doesn't understand the context of your project. That's your job, and it always will be.

The best vibe coders don't blindly accept AI output. They look at every result and ask: "Is this what I wanted? Does this serve the purpose? Would I be proud to show this to someone?"

If the answer is no, iterate. If you can't articulate why it's wrong, that's okay — "something feels off about this, make it feel more [X]" is a perfectly valid prompt.

Your taste is the filter that separates "AI slop" from "work that resonates."

Dark Flow

Momentum that masks lack of understanding.

Your relationship with frustration changes over time. Track where you are now — you can retake this later and see how you've grown.