← Back to Module 8 | Parent Guide | Course Home

Think Like a Coder: Complete Course Study Guide

A review of all 8 modules, key vocabulary, and skills learned

This study guide covers the entire Think Like a Coder course. Use it to review what you learned, look up vocabulary words, or remember key ideas from any module. You can print it and keep it as a reference!

All 8 Modules at a Glance

Module 1: What is Thinking Like a Coder?

Big Idea: Computers follow exact instructions, step by step. Coding is really about thinking clearly and giving precise instructions.

Computers do exactly what you tell them -- nothing more, nothing less
The Robot Game showed that vague instructions lead to unexpected results
Scratch is a visual coding tool where you snap blocks together
Thinking like a coder means being clear, precise, and logical

Module 2: Patterns Everywhere

Big Idea: Patterns are things that repeat or follow a rule. Spotting patterns helps you predict what comes next and find shortcuts.

Patterns appear in shapes, numbers, colors, music, and nature
Once you spot a pattern, you can predict what comes next
Patterns help coders write smarter, shorter code
In Scratch, you can create patterns using repeat blocks

Module 3: Step-by-Step Thinking

Big Idea: Decomposition means breaking a big problem into smaller, easier steps. A sequence is a set of instructions in a specific order.

Big problems become manageable when you break them into small pieces
The order of steps matters -- changing the order changes the result
An algorithm is a step-by-step set of instructions to solve a problem
In Scratch, sequences are blocks connected from top to bottom

Module 4: Making Decisions

Big Idea: Conditionals let you make decisions based on whether something is true or false. "IF this is true, THEN do that."

If/then thinking is how computers (and people) make choices
A condition is something that is either true or false
Decision trees help you map out all possible choices
In Scratch, the "if/then" and "if/then/else" blocks let sprites make decisions

Module 5: Loops and Repetition

Big Idea: Loops let you repeat actions without writing the same instructions over and over. They save time and make code shorter.

Repetition is everywhere -- in music, art, daily routines, and nature
A loop repeats a set of instructions a certain number of times (or forever)
Loops make code shorter and easier to read
In Scratch, "repeat" and "forever" blocks create loops

Module 6: Debugging -- Finding and Fixing Mistakes

Big Idea: Mistakes are clues, not failures. Debugging means finding and fixing errors in a calm, systematic way.

Every programmer makes mistakes -- even experts
A bug is a mistake in code that makes it do something unexpected
Debugging means finding the bug and fixing it
Strategies: read code carefully, test one thing at a time, check your assumptions
A growth mindset means believing you can get better with practice

Module 7: Building Something Real

Big Idea: Design thinking means planning before you build. Good creators ask WHO, WHAT, and HOW, then plan, build, test, and improve.

Design thinking: Think, Plan, Build, Test, Improve
A storyboard is a set of drawings showing your project scene by scene
Build and test in small steps -- do not try to do everything at once
Iteration means making something better each time you work on it
Kind feedback tells what is good AND suggests improvements

Module 8: Thinking Beyond Code

Big Idea: The thinking skills from coding help with everything -- writing, math, science, games, and everyday life.

Logic puzzles use the same skills as coding: step-by-step reasoning, testing, and elimination
Strategy games teach you to think ahead and plan moves
Decomposition helps with writing; patterns help with math; debugging helps with fixing mistakes
Thinking like a coder is a lifelong skill, not just a computer skill

Complete Vocabulary List

Word	What It Means	Module
Algorithm	A step-by-step set of instructions to solve a problem or complete a task	3
Backdrop	The background image in a Scratch project	1, 7
Brainstorming	Coming up with lots of ideas without judging them	7
Bug	A mistake in code that makes it do something unexpected	6
Code	Instructions written in a language that a computer can understand	1
Conditional	An instruction that checks if something is true or false and acts accordingly (if/then)	4
Debugging	The process of finding and fixing mistakes in code	6
Decision Tree	A diagram that shows different choices and where each choice leads	4
Decomposition	Breaking a big problem into smaller, easier pieces	3
Design Thinking	A way of planning that asks WHO, WHAT, and HOW before building	7
Event	Something that triggers code to run, like clicking the green flag or pressing a key	1, 4
Feedback	Telling someone what you think about their work in a kind and helpful way	7
Growth Mindset	Believing you can get better at something with practice and effort	6
Iteration	Making something better by trying, testing, and improving over and over	7
Logic	Thinking that follows clear rules and reasons step by step	4, 8
Loop	A set of instructions that repeats a certain number of times or forever	5
Pattern	Something that repeats or follows a predictable rule	2
Pattern Recognition	The skill of noticing patterns and using them to solve problems or make predictions	2
Scratch	A free visual coding tool from MIT where you snap blocks together to create programs	1-7
Sequence	A set of instructions in a specific order, where the order matters	3
Sprite	A character or object in Scratch that can move, talk, and change appearance	1, 7
Storyboard	A set of drawings that show what happens in a project, scene by scene	7
Strategy	A plan for how to win a game or solve a problem by thinking ahead	8
User Testing	Having someone else try your project to find confusing or broken parts	7

Key Skills You Learned

Skill	What You Can Do
Give precise instructions	Tell someone (or a computer) exactly what to do, step by step, without leaving anything out
Spot patterns	Notice when things repeat or follow rules, and use patterns to predict what comes next
Break problems into steps	Take a big, scary problem and turn it into a list of small, doable tasks
Make decisions with logic	Use if/then thinking to choose the right action based on what is true
Use loops for efficiency	Recognize when something repeats and use a loop instead of doing it manually every time
Debug calmly	Find mistakes without panicking, check things one at a time, and fix problems systematically
Plan before building	Think about WHO, WHAT, and HOW before starting. Draw a plan. List what you need.
Test and improve	Try your work, get feedback, and make it better. Repeat as many times as needed.
Think ahead	Consider what will happen next before you act. Plan your moves like a chess player.
Solve logic puzzles	Use clues, elimination, and step-by-step reasoning to solve tricky problems

Review Questions for the Whole Course

What does it mean to "think like a coder"?
Why is it important to give precise instructions?
Give an example of a pattern you see in everyday life.
What is decomposition and when would you use it?
Give an example of if/then thinking outside of coding.
Why are loops useful?
What is a bug, and how do you debug?
What are the three big questions in design thinking?
What is iteration?
How does coding thinking help with writing? With math? With science?
What was the most important thing you learned in this course?

Remember: Thinking like a coder is not about memorizing blocks or writing perfect code. It is about approaching problems with confidence, breaking them into steps, trying things out, learning from mistakes, and never giving up. You have proven you can do all of these things. Keep thinking like a coder!