Speaker Notes - Lesson 1

Share screen with a Snake game running in Preview - make sure the game is colorful and attractive "Hello everyone. I want you to put down your pens, leave your keyboards and just look at my screen." [Pause - let students focus] "You see that snake moving there? This game, the classic Snake, is something that until half a year ago, if you wanted to build it from scratch, your path would have looked like this:" [Dramatic pause] "You would sign up for a coding course, spend two months learning what variables are, what loops are, struggle with JavaScript syntax in technical English, and only after long months of frustration - maybe you'd manage to get a green square to move on a black screen."

"But the world has changed. The game you're seeing right now, I built in under 4 minutes."

"And the crazy part? I didn't write a single line of code. I didn't open a textbook, didn't Google 'how to build a game', and didn't deal with a missing semicolon on line 40."

"Welcome to the Game Development with AI course. In the next 40 minutes, I'm not going to teach you how to code. I'm going to teach you how to manage."

"Our approach today will be different: for the next half hour you don't do anything. You just listen and watch. I'll demonstrate the entire process, explain the logic, and only at the end we'll split into practice rooms."

"So lean back, make sure you can see my screen well, and let's begin."

Show the slide with two columns - old (red) and new (green) "Look at the difference. On the red side - the old world. Months of learning, struggling with bugs, and the result? A square that moves. On the green side - a new world. A few minutes, no code, and you get a complete game with design and colors."

"The sentence I want you to remember: We're not learning to code. We're learning to manage."

"Just like a CEO doesn't need to know how to weld steel to run a factory, you don't need to know JavaScript to build a game. You need to know what you want and how to ask for it."

"Before I open the software, we need to align on the language. There are three concepts you'll hear me say a lot."

"The first concept: IDE. In English it's Integrated Development Environment - your development environment."

"Think of it like a surgeon's operating table. The light is perfectly aimed, all the tools are arranged, the equipment is ready. This is the place where everything happens."

"Until now, development environments were intimidating. Lots of buttons, colorful text, technical English that only programmers understand. The tool we'll use - is different. It's not just a workspace, it's a workspace that already has the carpenter in it."

Open the software (New Window) - empty screen "Look at the screen. This is the software. This is what it looks like when it's empty."

"On the left – File Explorer. Currently empty, because we haven't created anything yet."

"In the center – Edit Area. Also currently empty."

"But the magic is on the right – the chat box with the agent. This is exactly where we'll work."

"Notice: in the old approach, I would need to create a file manually, name it index.html, and start writing code. In the new approach? I don't touch files. I go straight to the conversation."

"The second concept, and the most important: Agent."

"Until now you knew chatbots, like ChatGPT. You ask a question, it answers. That's nice, but it's passive."

"An agent is something completely different. An agent is an entity that knows how to perform actions. It doesn't just write text. It can create files, delete things, run tests." [Pause - let the idea sink in] "In our construction site analogy: if you used to have to build the wall yourself brick-by-brick, today you have a skilled worker. You don't need to know how to hold a trowel, you just need to know how to say: 'Build a 2-meter white wall'."

"The third concept: Prompt - the instruction. This is the language we speak with the agent."

"If you tell your worker 'build a house', you might get a tent or a palace. And that's probably not what you wanted." [Wait for smiles] "The art we'll learn here is how to write a precise instruction: 'Build a private house, one floor, red tile roof, wooden door'. The more precise we are, the better the agent works."

"Okay, I'm going to demonstrate now how to build the game from scratch. Pay attention to the structure of the prompt I write:"

"First component - Role: I start by telling the agent who it is. 'You are an expert game developer.' Why? Because this way it 'gets into character' and focuses on game development."

"Second component - Task: What do I want? 'Create a classic Snake game.' Simple, clear."

"Third component - Constraints: 'Generate a single file.' Why? Because we're just starting. No need for complications."

"Fourth component - Design: 'Dark background, Neon Green Snake.' Without this, it might have given us gray squares on a white background. And we want something that looks cool."

Type the prompt in the chat panel and press Enter "Watch what happens now. I raised my hands from the keyboard." [Physically emphasize - raise hands from keyboard] "You see the text running fast? That's the agent working. It's writing three languages simultaneously right now - HTML, CSS and JavaScript."

Wait for the code to finish, then click Preview "It's done. Now I click Preview..." [Click and let students see the result] "Wow. Look at that."

"Dark background? Yes. Glowing green snake? Yes. Score? Yes."

Play for a few seconds - move the snake, eat an apple "Let's play for a moment... the snake moves, it eats, it grows."

"In under 2 minutes, we created a working product."

"But... and this is a big but. This still isn't perfect. Games are never perfect on the first try."

"The agent just wrote code in three languages. Let's understand what each one does:"

"HTML - that's the foundation. Like a building's foundation - it determines that there's a 'game area' here, there's 'score text', there's a 'heading'."

"CSS - that's the design. This is what turns the foundation into something beautiful. The dark background, the glowing green snake, the arcade font - all CSS."

"JavaScript - that's the brain. This is what makes the snake move when you press an arrow. This is what makes it grow when it eats. This is what creates the logic of the game."

"You don't need to memorize all this. The agent knows all three languages. You just need to know they exist."

Play the game intentionally to hit a wall "Okay, I hit the wall. Notice what happened." [Point at the screen] "The snake just... stopped. No message. No Game Over. No Restart button. I have to refresh the whole page."

"From a user experience standpoint - this is bad. A player who encounters this will think the game is broken."

"In the old world, this is the moment the student gives up. They need to go into the code, find lines, understand, write a new function. But we're managers. We have an agent."

"The most important thing you'll learn: development is a cycle. 1. Build. 2. Test. 3. Improve. And repeat."

Type the second prompt in the chat "I go back to the chat and simply continue the conversation: 'The game is great, but when I crash into the wall, nothing happens. Please add a Game Over screen with the final score and a Restart button.'"

"Notice: I describe the problem and the solution. You don't need to be a programmer - you need to know how to say what's broken and what should happen."

Run and check - demonstrate that the problem is fixed "Let's check... There it is! A Game Over window appeared. The score is showing. There's a Restart button. We fixed a bug without touching code, in 20 seconds."

"Two last concepts for today:"

"Context Aware - did you notice the agent didn't rewrite the entire game? It's context aware. It read the existing code, understood what was there, and changed only what was needed. It's like asking a carpenter to fix a drawer in a cabinet - they don't build a new cabinet."

"UX - User Experience. How the player feels when using your product. The snake that stopped without a message? Bad UX. A nice Game Over screen with a Restart button? Good UX."

"As product managers, you need to be the player's representative. Play, feel what's not working, and ask the agent to fix it."

Stop screen sharing, switch back to full camera view "So what did we see here in the last 35 minutes?"

"We saw how to turn an abstract idea - 'I want Snake' - into a working product."

"We saw that code is no longer a barrier, but something that's generated for us."

"We learned that development is a process of dialogue - we request, test, and request fixes."

"Now - your turn."

"In a moment we'll open the rooms. In each room there will be a teaching assistant waiting for you. You have one simple task for the next 20 minutes: build your first Snake game."

"The process:"
"1. The teaching assistants will help you install the software."
"2. You'll get the prompt I used - I'm sending it in the chat now."
"3. Run it, see the game working."
"4. For advanced students: try changing one thing - color, speed, or text."

"Don't be afraid to make mistakes. If the agent writes bad code - ask it to fix it. That's part of learning."

"I want everyone to leave today's session with a game they built with their own hands on their computer."

"Ready to go from players to creators? Let's go, opening rooms. Good luck!"