Coding Playground

Code Explorer

Code Explorer: Coding is everywhere — in your phone, your games, traffic lights, and even the machines that help farmers water crops in rural Utah. Start your adventure by visiting Code.org and clicking "Try a one-hour tutorial." Choose the "Minecraft" or "Star Wars" themed Hour of Code. Don't rush — read every instruction. When a block snaps into place and something moves on screen, that's you telling a computer exactly what to do. After finishing, explore the CS Fundamentals course for free at studio.code.org/courses. Notice how code is just a list of very specific instructions — computers are powerful but they only do exactly what you tell them. You're ready for the next step when you can finish the Hour of Code tutorial and explain to someone what a "loop" does in your own words.

Puzzle Master

Puzzle Master: Ready to solve harder challenges? Go to Code.org's "Course D" or "Course E" (studio.code.org/courses) and work through at least 10 puzzle levels. Each puzzle gives you a goal — get the character to the star, water the plants, collect the gems — and a set of blocks to solve it. When you get stuck, don't click the hint right away. Stare at the problem for two minutes first. Real programmers call this "rubber duck debugging" — talking through the problem out loud helps your brain find the answer. Try solving the same puzzle two different ways: once with a loop, once without. Which uses fewer blocks? Fewer blocks usually means smarter code. You're ready for the next step when you've solved 10 puzzles and can explain why loops make code shorter.

Scratch Artist

Scratch Artist: Move to Scratch.mit.edu and create a free account. Build an animated art project: choose a Scratch sprite (character), add a background, and write a script that makes the sprite move, say something, and change its appearance. Use at least four different block categories: Motion, Looks, Sound, and Events. Make your sprite dance to a beat, draw a pattern using the Pen extension, or animate a short story. Scratch is used by millions of kids worldwide — and some professional animators started here. Visit the Scratch Explore page to see what other creators have made and remix one project by adding your own twist to it. You're ready for the next step when you have an original Scratch project published with at least three different block types working together.

Game Designer

Game Designer: In Scratch, build a playable game from scratch — no remixing this time. Design a game where the player controls something with the arrow keys or mouse. Your game must have: a way to score points, a way to lose (touching an enemy or falling off screen), and a "Game Over" message. Use variables to track the score — find them in the orange Variables category. Test your game by playing it yourself 10 times and fixing anything that feels unfair or broken. Then ask one other person to play it and watch their face — where do they get confused? Where do they have fun? A good game designer watches players, not the screen. You're ready for the next step when someone else can pick up your game, figure out how to play it without instructions, and reach a game-over state.

Debug Detective

Debug Detective: Bugs are mistakes in code that make it do the wrong thing. They're not failures — every programmer alive deals with them daily. Go to Scratch.mit.edu and search for "broken project" or "debug challenge" — find a project that has a bug intentionally built in. Figure out what's wrong by reading each script block carefully. Then go to Code.org and try the "Debugging" lessons in the CS Fundamentals section. Back in your own game from the last step, add one new feature. It will probably break something. Use Scratch's "See inside" and the step-through-code approach: comment out blocks one at a time to find the culprit. Write your bug and fix in your notebook. You're ready for the next step when you can find and fix a bug in someone else's Scratch project and explain exactly what was wrong.

Project Showcase

Project Showcase: Build your biggest project yet — a game, an interactive story, or a creative tool — that shows off everything you've learned. It must use: variables, loops, conditionals (if/then), and user input. Spend at least three work sessions on it. Give it a title screen, clear instructions, and a polished look. Publish it on Scratch.mit.edu and write a project description that explains what it does and one thing that was hard to figure out. Share the link with your school or post it in the Scratch forums under "Show and Tell." Try to get five people to play it and collect their comments. Then write a short "what I'd build next" paragraph — every great project is a stepping stone to the next one. You're ready for the next step when your published Scratch project has been played by five people and you've responded to at least two comments.