Lock In Lab Intern, rank 1 of 9

JR-3bugThird of 3 Junior Dev tickets

Read the error before you paste it

Takes
25 min in 3 steps
Checked
19 Nov 2026
min

Your estimate is optional. Your review compares it with how long it took; nothing is scored.

Pasting a 200-line error into the chat works, slowly. Finding the one line that matters works faster and teaches you the codebase. You'll make the agent build something that fails, and fix it with one targeted prompt.

You'll need Node.js installed (node -v). Any agent. Prices checked this month are on Tools.

Get a small Node project that fails

Step 1 of 3, about 5 min

Run node total.js. You should get a wrong total: text glued together, a number that's too small, or NaN, depending on how the agent wrote it. Commit this broken state; you're going to want to come back.

Paste this to your agent
Create a tiny Node script, total.js, that reads prices.json and prints the total. Then make prices.json with one price written as a string like "12,50" so the total comes out wrong. Don't fix it.

The part of a video worth watching for this step

YouTube, leerob. Published Apr 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Find the line that matters

Step 2 of 3, about 10 min

Read the output top to bottom. For a crash, the useful line is usually the first one that mentions one of your files with a line number, not a file inside node_modules. For a wrong result there's no stack trace at all, so you add one console.log before the sum and look at what's actually there.

The part of a video worth watching for this step

YouTube, Matt Pocock. Published Feb 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

the usual mistake

Assuming where the bug is. Look at the real data or the real header before you reason about it. It happened to us in INC-08, "Login returns 200 and the session never starts".

One prompt, then verify

Step 3 of 3, about 10 min

Run it again. Then put a garbage value like "abc" in the file and check it fails loudly instead of quietly.

Paste this to your agent
prices.json has "12,50" as a string and total.js adds it as-is, so the total is wrong (paste exactly what it printed). Parse comma decimals correctly and reject anything that isn't a number.

The part of a video worth watching for this step

YouTube, DevForge. Published Feb 2026.Checked 19 Nov 2026

Optional. The step counts when you've done it, whether or not you watch. Minutes from the creator's chapters; our notes on this video.

Check and ship

The whole ticket
Run:
node total.js

It passes when The correct total. With "abc" in the file, a clear error message instead of NaN.

  • You found the first line of the error that names a file in your project, and the line number.
  • The fix took one prompt that quoted that line, not the whole log.
  • The command that failed now passes.

No server checks your work in this version: you mark it, and your review says "Checked by you". Graded checks are planned for Plus.

Next: SH-1 A form that saves, without leaking everyone else's rows

What do you see?

Pick the closest one. Each goes to what to try first and the incident it looks like.