How to actually learn programming
Programming is a procedural craft: it lives in your hands, not in your notes. Watching a course fluently is not the same skill as writing code, which is why so many people finish three tutorials and still freeze at an empty editor.
The method
Build progressively harder working things, reading the errors as the lesson rather than as failure.
Write and run code: extend a working program, fix a broken one, refactor a rough one.
Where it goes wrong
Nothing runs and the error message explains nothing.
Treat the error as the lesson. A stack trace read slowly teaches faster than a paragraph of theory — and a tutor should make you run the code, not just show it.
Tutorials work, but a blank file is paralysing.
Shrink the problem before adding explanation. A smaller thing that runs beats a bigger thing explained — then build on it tomorrow.
What mastery actually looks like
Not a grade — observable abilities. A plan should be able to say which of these it has evidence for:
- Can build — writes working code for a stated problem without a template.
- Can debug — locates and fixes a defect from the symptom alone.
- Can design — chooses a structure that holds up as requirements change.
- Can read code — explains what unfamiliar code does and why.
Keeping it
Keep building on what already exists — code you return to is code you remember.
Common questions
Can I learn programming by watching videos?
Videos explain; they do not train. In a build discipline roughly half of study time should be spent writing and running code, with lessons there to explain what you just built — not the other way round.
Why do I understand tutorials but can't start from scratch?
Tutorials remove the hardest skill — decomposing a problem into steps. The fix is deliberately starting from smaller blank files, not consuming more tutorials.
How often should I practise code?
Short and frequent beats long and rare: the engine schedules build subjects as one explanation followed by two working sessions, then consolidation.
Engine values reviewed 2026-09-01. Related: engineering, cybersecurity, a language.
Akiri turns this into your actual week: tell it your goal and your date, and it measures where you're starting from, builds the plan backwards from the deadline with this discipline's own rhythm, and rebuilds it as you go — in English, French, Spanish, Hindi or Chinese.