Understand why having your code generated destroys learning, and adopt the golden rule: the AI explains, you write.
Open this lesson in KodokonHere is the most dangerous scene of your learning journey. You have an exercise: write a function that counts the vowels in a word. You paste the instructions into the AI, it produces perfect code in three seconds, you copy it, the exercise is "done". Everything seems won: it was fast, the code works, you even vaguely understood it while reading it. In reality, you just skipped your training session. The next day, faced with a blank page, you would be unable to rewrite that function.
This isn't an opinion, it's a classic finding of memory research. The generation effect, documented by many studies since the 1970s, shows that we remember far better what we produce ourselves than what we merely read. Searching, hesitating, making mistakes, correcting: it is this effort that etches knowledge into memory. Researchers Robert and Elizabeth Bjork gave this principle a name: desirable difficulties - the obstacles that make learning slower in the moment, but far more durable. Having the solution generated removes exactly that difficulty… and therefore the learning along with it.
Hence the golden rule of this course, to apply to every exercise: the AI explains, YOU write. Concretely: ask it to clarify a concept, to give you a hint, to ask you questions, to review YOUR code and point out your mistakes. But every line of code that counts toward your learning must come from your fingers, not from its. Compare the two uses below - same exercise, opposite fates.
Write me a JavaScript function that counts the vowels in a word.Good use turns the AI into a tutor: it marks out the path, but you are the one who walks it. The following prompt is the most important of the course - keep it safe, it works for any exercise.
You are my programming tutor. I'm a beginner and I want to LEARN, not to get the solution.
Here is my exercise: write a JavaScript function that counts the vowels in a word.
Absolute rules, valid for the whole conversation:
1. NEVER write the solution for me, not even partially, even if I ask you to.
2. Help me step by step: first ask me questions so that I break the problem down myself.
3. When I get stuck, give me an increasingly precise hint, never the code.
4. When I show you MY code, point to the line that's causing a problem and ask me what it does, instead of fixing it.
5. At the end, give me a similar exercise to check that I can do it on my own.
Start with your first question.