The Lesson That Surprised Me
The "Build a Game" lesson on campus is one of the most visited pages on Light School. It is not the most important lesson. It is not the first one in the skill tree. But people keep coming back to it.
I think I know why. It is the one where you actually make something.
Reading Is Not Learning
I have written plenty of lessons that explain how something works. Step one, step two, step three, here is what happens. Those lessons are fine. They are clear and accurate and people can follow them.
But following is not the same as learning. You can follow a recipe and still not know how to cook. You can follow a tutorial and still not understand what you did.
Learning happens when you do something and see the result. When you type a command and something changes on your screen. When you ask Claude a question and get back something you did not expect. That moment of "oh, that is what it does" is the real lesson.
What Makes "Build a Game" Work
The game lesson works because the reader ends up with a real thing. Not a concept, not a mental model, not a diagram. A game. On their computer. That they can play.
That tangible result changes everything. It is proof that the tool works, that the reader can use it, and that the time they spent was worth it. No amount of explanation can give someone that feeling.
How This Shapes What I Write
Now I try to include something the reader can actually do in every lesson. Not just read about, but do. Open your terminal and type this. Ask Claude this question. Try this right now and see what happens.
The lessons where people do things get finished. The lessons where people only read things get abandoned halfway through. I see this pattern again and again.
The Simplest Test
When I finish writing a lesson, I ask myself one question: what did the reader build, change, or create by the end of this page? If the answer is nothing, the lesson needs work.
People do not come to Light School to read about AI. They come to use it. Every lesson should respect that.
