Learning and making
From vibecoding to actually coding
You can build something that works with an AI assistant — and you suspect you do not understand what appeared under your hands. This closes that gap without asking you to stop building.
What the plan does
Keep building with the assistant, under one rule: nothing you cannot explain line by line. Plus reading other people's code, debugging without help, and fundamentals in the order they actually bite.
Who it is for
For anyone who has vibecoded something and does not want to stop there. Complete beginners included — most people start this way now.
How the plan runs
Read code and trace it by hand
Explaining someone else's file is a faster route than writing from scratch. The rule the whole plan rests on: nothing goes further that cannot be explained line by line.
Debug deliberately
Reproduce, isolate, form a hypothesis — instead of pasting the error back into the assistant.
How the language actually works
Types, scope, references, async. Then data and state: where the truth lives and what can change it.
Judge a suggestion
Spot the version that works today and breaks in six months. Plus short sessions with no assistant — not as punishment, but as the only way to find out what you actually know.
When you fall behind
Theory gets cut. Building and explaining stay.
What we will ask you
- What have you built?
- Where do you get stuck most often?
- How many hours a week do you have?
The plan is built around your answers: broken down into years, months, weeks and finally today. With rest written into it, and recalculated every time the route and reality part ways.
Start with this template