Vibe Coding · 강의

오류 메시지 이해하기

오류를 인공지능에 붙여 넣기 전에 먼저 읽어보십시오.

오류 메시지 이해하기은(는) CoddyKit의 무료 Vibe Coding 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Vibe Coding 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Errors Are Clues, Not Walls

When you're building with AI and something breaks, your screen fills up with red text. It feels scary. But here's the truth: an error message is a clue, not a wall.

The computer is literally telling you what went wrong and where. Once you learn to read these clues, debugging becomes a conversation instead of a panic. And when you pair that skill with AI, you'll fix bugs faster than most experienced developers.

In this lesson, you'll learn to read errors before you paste them to tools like Cursor, Claude Code, or Copilot.

Anatomy of an Error

Most error messages have three parts you should hunt for:

The type — what kind of problem (e.g. TypeError, ReferenceError)
The message — a short human-ish description
The location — file name and line number

Here is a classic JavaScript error. Read it slowly, left to right.

TypeError: Cannot read properties of undefined (reading 'name')
    at showUser (app.js:14:22)
    at main (app.js:30:3)

Decode That Error

Let's decode the error from the last scene piece by piece:

TypeError → the kind of bug: we used a value the wrong way
Cannot read properties of undefined (reading 'name') → we tried to grab .name off something that doesn't exist
at showUser (app.js:14:22) → it happened in the showUser function, file app.js, line 14, column 22

That last part is gold. You now know exactly where to look: line 14.

The Stack Trace

The list of at ... lines is called the stack trace. Read it top to bottom: the top line is where the error actually exploded, and each line below shows what called it.

Beginners often paste the whole thing to AI and ignore it. But just glancing at the top line tells you which function to inspect first. The lines mentioning your own files matter most — lines deep in libraries are usually not your bug.

at showUser (app.js:14:22)   ← your code, START HERE
at main (app.js:30:3)        ← your code, who called it
at node_modules/.../run.js   ← library, usually ignore

See an Error Happen Live

Let's actually trigger one. Run this snippet. It tries to read .toUpperCase() on a value that is undefined, which throws the same family of error.

Read the message it prints — notice how it names the exact problem.

const user = { email: "ada@example.com" };
try {
  console.log(user.name.toUpperCase());
} catch (err) {
  console.log("Error type:", err.name);
  console.log("Message:", err.message);
}

Common Error Types

You'll meet the same handful of errors over and over. Knowing them on sight saves time:

SyntaxError — a typo the computer can't even read (missing bracket, comma)
ReferenceError — you used a name that doesn't exist (typo'd variable)
TypeError — a value exists but you used it the wrong way
RangeError — a number or length is out of bounds

When you can name the error type, you can tell AI what category of fix you need.

Read Before You Paste

Here's the habit that separates fast builders from frustrated ones: read the error for 10 seconds before reaching for AI.

Ask yourself three quick questions:

What's the error type?
What file and line does it point to?
What was I just doing when it broke?

Even if you still hand it to AI, answering these makes your prompt far sharper — and you'll often spot the fix yourself before AI even replies.

Errors Point at the Symptom, Not Always the Cause

One subtle trap: the line in the error is where things blew up, but the real cause might be earlier. In our example, line 14 reads user.name — but the actual bug might be that user was loaded wrong on line 8.

So treat the error location as your starting point, then trace backwards: where did this value come from? AI is great at this once you point it to the right region.

Browser vs Terminal Errors

You'll see errors in two main places:

Browser Console (press F12, click Console) — for front-end web code. Click the file:line link and it jumps you right to the code.
Terminal — for back-end / Node.js / build tools. Same anatomy, just no clickable link.

Tools like Replit, Bolt, and Cursor often surface these inline and even add a 'Fix with AI' button. But that button works best when you already understand the message.

A Quick Reading Drill

Read this error and try to answer in your head before scrolling: What type? What line? What's missing?

Answer: It's a ReferenceError — the variable totl doesn't exist (a typo for total) — on line 7. The fix is a one-character spelling correction. No AI needed, just careful reading.

ReferenceError: totl is not defined
    at calculateCart (cart.js:7:18)

Turn Reading Into a Reflex

Run this final example. It deliberately misspells a variable. Watch the console name the exact problem — then imagine how fast you'd fix it knowing how to read it.

The goal isn't to memorize every error. It's to build the reflex: stop, read the type, read the line, then act.

const total = 42;
try {
  console.log(totl); // typo on purpose
} catch (err) {
  console.log(err.name + ": " + err.message);
}

Quick Check

You see: TypeError: Cannot read properties of undefined (reading 'name') at showUser (app.js:14:22). Where should you look FIRST?

Recap: You Can Read Errors Now

You leveled up from 'red text = panic' to 'red text = clue'. You learned to:

Spot the error type, message, and location
Read a stack trace top-down and focus on your own files
Recognize common types: Syntax, Reference, Type, Range
Treat the error line as a starting point, then trace backwards

Next up: how to take this understanding and paste errors to AI effectively so it fixes the bug on the first try.

자주 묻는 질문

“오류 메시지 이해하기” 강의는 무료인가요?

네 — “오류 메시지 이해하기” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Vibe Coding 강의 전체를 잠금 해제할 수 있습니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.

“오류 메시지 이해하기”에서 뭘 배우나요?

오류를 인공지능에 붙여 넣기 전에 먼저 읽어보십시오. 브라우저에서 직접 실행하는 실습 코드로 Vibe Coding을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Vibe Coding을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Vibe Coding은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“오류 메시지 이해하기” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Vibe Coding 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Vibe Coding 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Vibe Coding(으)로 돌아가기