유지, 수정 또는 거부
무엇을 남길지 결정하고 더 나은 결과를 요청합니다.
유지, 수정 또는 거부은(는) CoddyKit의 무료 Vibe Coding 강의입니다. 이것은 4개 중 4번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Vibe Coding 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
The Decision That Makes You a Builder
You've read the AI's code and spotted possible issues. Now comes the part that actually ships products: deciding what to do about it.
Every chunk of AI code lands in one of three buckets: Keep it, Fix it, or Reject it. Making that call quickly and confidently is the core review skill.
This lesson gives you a simple framework so you never just blindly hit 'Accept All' again.
The Three Buckets
Here's the whole framework in one view:
- Keep: it does what you asked, you understand it, no obvious risks. Accept it.
- Fix: it's close but has a bug, a missing case, or messy bits. Ask AI to adjust it.
- Reject: it's wrong-headed, overcomplicated, or doesn't match your goal. Throw it out and re-prompt.
Most code is 'Keep' or 'Fix'. Reject is rarer but powerful — don't be afraid to use it.
When to KEEP
Keep code when all three are true:
- It does what you asked when you run or trace it.
- You understand it enough to change it later.
- You don't see obvious bugs or risks from your bug scan.
The function below is clean, named well, and does exactly one clear thing. This is a confident Keep.
function formatPrice(amount) {
return '$' + amount.toFixed(2);
}
console.log(formatPrice(9.5)); // $9.50
console.log(formatPrice(12)); // $12.00When to FIX
Fix when the code is mostly right but has a specific flaw you can name. You're not starting over — you're steering.
This code works for normal input but crashes on an empty cart. That's a clear Fix: keep the structure, patch the gap.
function cartTotal(items) {
return items.reduce((sum, i) => sum + i.price, 0) / items.length;
// bug: average not total, and crashes on empty cart
}
console.log(cartTotal([{ price: 4 }, { price: 6 }])); // 5, not 10!How to Ask for a Fix
Good fixes come from specific requests. Don't say 'make it better' — name the exact problem so AI doesn't rewrite the whole thing or wander off.
Point at the precise issue, like this:
Fix two specific bugs in cartTotal, keep everything else the same:
1. It divides by length — I want the TOTAL, not the average.
2. It crashes on an empty cart — return 0 instead.
Show only the corrected function.When to REJECT
Reject and re-prompt when fixing would be more work than restarting. Red flags for rejection:
- It solves the wrong problem entirely.
- It's a tangled mess you can't follow.
- It uses invented libraries or fake functions.
- It quietly ignored a key requirement you stated.
Rejecting isn't failure — it's faster than patching something broken at its core. In Cursor or Claude Code, just don't accept the diff and re-prompt.
Rejecting Well: Re-Prompt with Lessons
When you reject, don't just say 'try again' — tell the AI what went wrong so the next attempt is better, not the same.
Fold your finding into a sharper prompt:
That version doesn't work for me. Problems:
- It sorted oldest-first; I need NEWEST first.
- It imported a package that doesn't exist.
- It's way more complex than this needs to be.
Start over: simplest possible solution, newest-first, only built-in JavaScript, and explain your approach in one sentence first.Small Chunks Make Decisions Easy
The secret to fast Keep/Fix/Reject calls: review in small pieces.
If you let AI write 200 lines at once, your only options are 'accept the whole mess' or 'reject everything.' But if you build one function at a time, each decision is tiny and clear.
Prompt in steps: 'First just the function to fetch data. Show me, I'll review, then we'll add the display.' Small chunks = confident reviews.
Trust Your Gut, Then Verify
If something feels off — too complex, too clever, doesn't quite match what you pictured — that instinct is worth listening to.
You don't have to prove it's broken to ask for better. A quick 'this feels overcomplicated, can you simplify?' costs nothing and often improves the code a lot.
You're the decision-maker. The AI proposes; you dispose. Comfortable saying 'no, again' is a superpower.
A Worked Example
Let's apply the framework to one real chunk. You asked AI for a function that returns the most recent post. It hands you this:
Trace it: it sorts by date but oldest-first, then grabs index 0 — so it returns the oldest post, the opposite of your goal. The structure is fine, the bug is specific and nameable.
Verdict: Fix. Keep the shape, just flip the sort. You'd reject only if it were tangled or solving the wrong task entirely.
function latestPost(posts) {
const sorted = posts.sort((a, b) => a.date - b.date); // oldest first!
return sorted[0]; // returns the OLDEST, not the latest
}
// Fix: sort newest-first (b.date - a.date), and guard empty listYour Keep / Fix / Reject Checklist
Run this for every chunk of AI code:
- Does it match my goal? If no → Fix or Reject.
- Do I understand it? If no → ask to explain, then Fix or Reject.
- Any bugs or risks? If yes → Fix.
- Is it a tangled mess or wrong-headed? If yes → Reject and re-prompt.
- All clear? → Keep, and move on.
This loop, on small chunks, is how reliable apps get built with AI.
Quick Check
AI generates a function that's mostly correct but crashes on an empty list and computes an average when you wanted a total. What's the right call?
Recap: Keep, Fix, or Reject
The decision framework you now own:
- Keep when it matches your goal, you understand it, and it's risk-free.
- Fix when it's close — name the exact bug and ask AI to patch just that.
- Reject when it's wrong-headed or tangled; re-prompt with what went wrong.
- Review small chunks so every decision stays easy and clear.
- Trust your gut — you're the decision-maker; the AI proposes, you dispose.
You've now learned to review, read, debug-spot, and decide on AI code. That's the discipline that makes vibe coding ship real, working products.
AI 튜터와 함께 JavaScript을(를) 배우세요 — 무료
브라우저에서 실제 코드를 작성하고 실행하며, 24/7 AI 튜터로부터 즉각적인 도움을 받고, 웹이나 앱에서 중단한 부분부터 계속 학습하세요.
- 코스
- 25
- 레슨
- 100
자주 묻는 질문
“유지, 수정 또는 거부” 강의는 무료인가요?
네 — “유지, 수정 또는 거부” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Vibe Coding 강의 전체를 잠금 해제할 수 있습니다. Vibe Coding 강의에는 총 4개의 강의가 포함되어 있습니다.
“유지, 수정 또는 거부”에서 뭘 배우나요?
무엇을 남길지 결정하고 더 나은 결과를 요청합니다. 브라우저에서 직접 실행하는 실습 코드로 Vibe Coding을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Vibe Coding을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Vibe Coding은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 4번째 강의입니다.
“유지, 수정 또는 거부” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Vibe Coding 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Vibe Coding 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.