Why Most Students Learn Technology the Wrong Way
Watching tutorials feels like progress. Building something that breaks, and fixing it, is progress.
I teach programming, and the pattern repeats every year. Students complete long tutorial series, feel confident, then freeze in front of an empty file. Nothing was wrong with the tutorials. The problem is that following along exercises recognition, and building exercises recall — and only recall survives the exam, the interview, and the job.
The cheapest fix is to change what a study session looks like. Watch or read for twenty minutes, close the material, and rebuild the idea from memory in your own project. It will be slower and more frustrating, and you will retain considerably more of it.
The second fix is to let things break. A student who has debugged their own broken database connection understands connections in a way that a student who copied a working config never will. Error messages are the curriculum, not an interruption to it.
Finally, finish things. A small completed project teaches deployment, edge cases, and the unglamorous last ten percent. Ten half-finished projects teach the same opening chapter ten times.