Lesson 3: Don’t trust the machine 100%, verification loops and parallel sessions

After this lesson, you'll grasp the philosophy that separates great AI users from mediocre ones: when you hand off work, attach a way to verify it. Along with it come two practical skills: giving feedback so the machine fixes the result accurately, and running several Claude Code sessions in parallel without getting confused.

AI's real value isn't in getting it right the first time

Let's state plainly a truth that people selling AI courses like to hide: AI almost never gives a perfect result on the very first try. The first version usually reaches about 80%. Beginners see that, get disappointed, conclude “AI is useless”, and quit.

But look at how people work: a skilled craftsman might get it 100% right the first time, at the cost of 5 hours. The machine gives an 80% version in 2 minutes, and what pays off is that it can retry hundreds of times faster than a human: fix, check, fix again, each round taking just a few dozen seconds. Let it loop four or five rounds, 5 minutes in total, and the quality reaches what the craftsman took 5 hours to make. AI's value lies in iteration speed, not in the first shot.

To get that, the way you hand off work needs all three beats: hand off the work, let the machine do it, then make the machine verify its own result. A mediocre user has only the first two beats: hand off, receive the result, hand off the next. Missing the verification beat throws away most of the tool's value.

What verification means depends on the type of work:

• Building a website or interface: have the machine screenshot its own result then compare against the sample, list the differences yourself and fix them yourself (the same loop you saw in lesson 2).
• Writing a data-processing program: make the machine write automated tests alongside it then run them with sample data, fixing itself until it passes every test.
• Text work: make the machine check against the original requirement list line by line before reporting it's done.

At MONA we have a catchphrase for this: “looks done” isn't done. When the machine says it's done, it has to come with evidence: screenshots, test run results, a comparison table. Demand proof the way you'd demand a numbers report from an employee, and don't accept a bare report.

Giving feedback to the machine: talk like you would to a craftsman, the more specific the faster it's done

Once you have the 80% version, your part is giving feedback. Hard-won experience: gather all your comments into one go, pointing at each exact spot, instead of dribbling out one sentence at a time. For example, a good round of feedback for the website you just built:

“The logo in the left corner is too big, shrink it. The main headline is too bold, try a serif font and see. The portrait photo is cropped across the forehead, move it down and shrink it so the whole face fits in the frame. The button in the middle of the photo does nothing, either make it open the video or remove it. The customer review block is shifted left, center it. Change the copyright year in the footer to 2026.”

Six points in one round, and the machine fixes them in one pass. A tip that makes it three times faster: speak instead of typing. People type 50-70 words a minute and speak almost 200. Using a speech-to-text tool, you “unload” the whole stream of comments as if you were standing next to the craftsman's desk, and the machine understands it all.

Running multiple sessions in parallel: the real power of the terminal

This is when the “practice using the terminal” advice from lesson 1 pays off. Claude Code is not limited to one session: you open two or three terminal windows, each running a session on a different job. Lesson 2 built a website in a few minutes, so opening three sessions means building three options at once, then putting them side by side to pick your favorite. This flips the traditional habit of buying design: instead of waiting for one version and then revising back and forth, you have the machine produce three versions and choose.

But running in parallel has its price, and we want you to know it upfront so you aren't disillusioned:

• A beginner's brain is the bottleneck. Jumping back and forth between sessions takes a lot of focus. A self-check question: are the sessions actually running or are most of them sitting waiting for your next command? If the machine waits on you more than 10-20% of the time, you've opened too many sessions. Even experts only run 3-4 sessions comfortably on work that needs thinking.
• Start with 1 session, and move up to 2-3 once you're comfortable. Orchestrating multiple agents is a skill you build gradually, just like managing multiple employees: if you haven't finished managing one person, don't take on three more.
• Later (lessons 9 and 10) you will learn the tools made for exactly this: sub-agents, agent teams and git worktrees, which let you run in parallel in an organized way instead of opening windows by hand.

Don't forget the phone version

A mistake beginners building websites often make: only admiring the result on a computer screen. Yet in Vietnam, most of your customers open websites on their phones. Your command needs one more verification beat: “check the phone display, take a portrait screenshot for me to look at, and fix any text that overflows or any image that's distorted.” The machine can do all of it, as long as you remember to ask.

Try it yourself before moving on to lesson 4

1. Take the website you built in lesson 2 and draft one round of feedback with 5-6 points that are specific, then have the machine fix them in one pass.
2. Make the machine verify the phone version itself and provide screenshots as proof.
3. Try opening a second Claude Code session and build a second option of the same website with a different reference image. Compare the two versions.

Lesson 4 opens a door that most Claude Code users have never opened: the .claude folder with settings, hooks, rules, plus the working modes (plan mode, the skip-permission-prompts mode) and the set of slash commands. Once you understand lesson 4, you belong to the 10% of users who grasp this tool's deeper toolkit.