Lock In Lab Intern, rank 1 of 9

Rain outside.Three ticketson the desk.

Lock In Lab is a job you learn on. You take tickets, a coding agent writes the code, and a check decides whether it works. You start as the intern.

Day one75 min, saves as you go

  1. INT-1Make your first change with an agent, then undo it25 min Take INT-1
  2. INT-2Make a save point, break the page on purpose, roll it back25 min
  3. INT-3Write the spec before you ask for code25 min
62%
Lock in 25:00 Optional. It pauses.
No account. Nothing asked.

Nine ranks, and nobody moves up for watching videos.

A promotion is a list of things you've shown you can do: tickets shipped, an agent's pull request reviewed, incidents fixed with the postmortem written. Six ranks are open. The top three are still being written.

The whole ladder, with every requirement

Some nights the pager goes off.

Sixteen incidents, all from 2026, all ours. We took out the names and kept the rest. From rank four they page you: five come with a repo that reproduces the failure and a check that stays red until you fix it.

INC-01The bot that graded its own homeworksev 1
What we saw
A support assistant for a home-services business passed 40 hand-written tests. Asked "I smell gas near my furnace and I feel a bit lightheaded", it answered with the "I'm not a doctor, call emergency services" message instead of "leave the building, don't touch switches, call the gas company".
The rule now
Whoever builds doesn't grade. Test cases come from the spec or from a second agent with a different brief, and they combine conditions the spec lists separately: hazard plus symptom, urgent plus out of hours.
The full postmortem and the repo, 8 Sep 2026
INC-02We rolled back a safety fix because a sentence changedsev 2
What we saw
The gas fix from incident 1 disappeared the same afternoon. An automated guard had reverted it.
The rule now
Anything that can undo work needs the same proof as the work it undoes. Same bench before and after, or it isn't a measurement.
The full postmortem, 8 Sep 2026
INC-03The deploy job was green and the site was downsev 1
What we saw
Push, the deploy job goes green, the site returns nothing. About ten minutes offline. Then it happened again the same day, for a different reason.
The rule now
Reproduce the build from a clean clone (`git clone . /tmp/x`), never from your working folder. After every push, ask the live site which version it's running.
The full postmortem and the repo, 6 Oct 2026
INC-04Connection error that wasn't the networksev 2
What we saw
Every call to the AI provider failed with "Connection error", but only inside the container. On the laptop, fine.
The rule now
Empty is not unset. Treat `""` as missing in your own config code, and read the cause of an error, not just its message.
The full postmortem and the repo, 5 Sep 2026
INC-05437 rows processed, zero results savedsev 2
What we saw
A batch job ran an AI check over 437 rows. The stats said 437 verdicts written. The database had none.
The rule now
Verify by writing and re-reading from another session, not by reasoning and not by trusting your own counters.
The full postmortem, 5 Sep 2026
INC-06The bill didn't come from the volumesev 3
What we saw
Our cost report for an AI pipeline was 2.4 times higher than reality, and the real bill still went up about tenfold in a week.
The rule now
Measure cost per task from day one, including cache. Reprocessing every row after a prompt change is what costs money.
The full postmortem, 6 Sep 2026
INC-07The most expensive model gave the worst resultssev 3
What we saw
Switching an extraction task to a pricier model made it worse. One field meant to capture "money signals" was right 30% of the time.
The rule now
The contract (prompt plus automatic verification of quotes) matters more than the model. Build a labelled reference set before you change anything.
The full postmortem, 5 Sep 2026
INC-08Login returns 200 and the session never startssev 2
What we saw
Sign-in answered 200 OK and redirected, and every following page acted as if you were signed out.
The rule now
Look at the real header before you reason about the code.
The full postmortem and the repo, 3 Sep 2026
INC-09The page loads and no button does anythingsev 3
What we saw
The dev server served the page, everything looked right, and nothing responded to clicks.
The rule now
Spend three seconds on diagnosis before you touch code: does the production build behave the same?
The full postmortem, 3 Sep 2026
INC-10Healthcheck red, app perfectly finesev 3
What we saw
The container was marked unhealthy and restarted in a loop. Opening the app in the browser worked.
The rule now
Run checks inside the real container, not on your machine.
The full postmortem, 2 Aug 2026
INC-11Freeing port 8000 shut down Dockersev 2
What we saw
Every local container stopped at once.
The rule now
Look at what a process is before killing it. Block destructive commands with a hook, so asking nicely isn't the only protection.
The full postmortem, 3 Sep 2026
INC-12Seven agents at once, quota gone by mid-morningsev 3
What we saw
All sessions stopped with usage limits before 11:00 on a working day.
The rule now
Run only as many agents as you can actually review.
The full postmortem, 17 Nov 2026
INC-13Our setup script replaced the CI that ran the testssev 2
What we saw
Deploys kept working. They just weren't running tests any more.
The rule now
Read the diff of what your own scripts commit, the same way you'd read an agent's.
The full postmortem, 16 Nov 2026
INC-14Secrets in git, across dozens of repossev 1
What we saw
Nothing visible. That's the problem.
The rule now
`.gitignore` from the first commit, a secret scanner before every commit, and keys never pasted into a chat. A deleted file is still in history.
The full postmortem, 16 Nov 2026
INC-15The cause we found by elimination was wrongsev 3
What we saw
A simulation collapsed after a harmless-looking change. We ruled out the other explanations and settled on one.
The rule now
A cause reached by ruling out others is a hypothesis. Prove it with a control and criteria written in advance.
The full postmortem, 18 Aug 2026
INC-16The backup rotation deleted the only good backupsev 1
What we saw
Restoring yesterday's backup: every recent file was empty.
The rule now
Only verified things count. Count a backup after an integrity check passes, and restore from one now and then.
The full postmortem and the repo, 19 Nov 2026

All sixteen, with the repos

We marked the minutes so you can start at 4:20.

YouTube, Tina Huang. Published May 2025, 33 min.Checked 19 Nov 2026

Vibe Coding Fundamentals In 33 minutes

A structured intro with an example PRD, version control, debugging and two tool demos. The planning and debugging parts hold up; the tool demos are what has aged.

Every video is free to watch, always. Each one opens at the minute a ticket needs and says which parts no longer hold. Minutes come from the creator's own chapters. All 50.

What people earn from this, and who says so.

Most revenue numbers in builder videos come from the builder. We label each one and never upgrade a label.

ProductBuilt byRevenueSays whoWhere we read it
PostizNevo David$440,902 MRRVerified, StripeTrustMRR
Post BridgeJack Friks$48,567 MRRVerified, StripeTrustMRR
TrustMRRMarc Lou$11,992 MRRVerified, StripeTrustMRR
Base44Maor Shlomosold to Wix, about $80M up frontVerified, buyerWix press room
LovableAnton Osika$10M ARR two months after launchReported, presslennysnewsletter.com
GeoSportsFrank$40K a monthDeclared, his wordthe video
DaymakerWilliam Lindholm$150K a yearDeclared, his wordthe video

Figures read on 19 Nov 2026 at the linked source. Twenty stories, each with its video and what to take from it.