Manuals / Academy / Lesson 4

Reading errors without fear

An error isn't the computer telling you off. It's the computer telling you exactly what stopped it — which is the most useful thing it could possibly do. Once you see them that way, errors stop being scary and start being directions.

The truth about errors

Three things that take all the fear out:

How to read one

You don't read it like a book. Two quick instincts:

You don't need to decode the rest. That's the next step's job.

The two-minute fix

This is the same debugging superpower from Lesson 1 — worth burning into muscle memory:

  1. Select the whole output. In the Mac Terminal: ++A.
  2. Copy it. +C.
  3. Paste it to the AI and add one line: "This errored — what does it mean and how do I fix it?"
  4. Do what it says, run it again, and if it complains again, repeat. Clear the screen between tries with Ctrl+L.
You will routinely fix things you don't understand. That's not cheating — that's the whole point. Understanding comes later, from doing; it isn't a prerequisite.

Common ones, in plain words

You see…It means…
command not foundThat tool isn't installed yet. Install it (see Set up your computer) and try again.
permission deniedYou're not allowed to do that as-is — often needs admin rights, or you're in the wrong folder.
401 / 403 / unauthorizedAn access problem — a missing, wrong or expired token/password.
404 / not foundThe address or path is wrong — a typo in a URL, site or form name.
missing_fields / requiredSomething mandatory was left blank — fill it and resend.
A long red stack traceLooks alarming, isn't. Copy the lot and paste it to the AI — that's exactly what it's for.

What's next