Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Explain source vs machine code.
- ✓Compare compiler & interpreter.
- ✓See the tradeoffs.
- ✓Classify real languages.
How does the code you type actually get run by a computer?
How Code Runs
Project each item and have students answer about compilers and interpreters.
55 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — Lost in Translation
Your computer does not speak Python — so how does it run it?
👩🏫 Teacher Moves
- Pose the question.
- Share ideas.
- Set the goal.
🎒 Student Actions
- Think.
- Share.
- Get ready.
Use — Compilers & Interpreters
Students learn.
👩🏫 Teacher Moves
- Send students to How Code Runs.
- Note translation to machine code.
- Note compiler vs interpreter.
🎒 Student Actions
- Answer.
- Note it.
- Note it.
Modify — Trace It
Students practice.
👩🏫 Teacher Moves
- Say what a compiler does.
- Say what an interpreter does.
- Name a tradeoff.
🎒 Student Actions
- Say.
- Say.
- Name.
Create — Classify It
Students apply.
👩🏫 Teacher Moves
- List a few languages.
- Mark compiled or interpreted.
- Say one effect of each.
🎒 Student Actions
- List.
- Mark.
- Say.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- Define machine code.
- Compiler vs interpreter?
- Complete the exit ticket.
🎒 Student Actions
- Say it.
- Say it.
- Complete the exit ticket.
Built to the standards you report on
Aligned to the CSTA K-12 Computer Science Standards and the ISTE Standards for Students.
Explain levels of abstraction and translation.
Explain how abstractions hide complexity.
Evaluate how programs are executed.
Understand how systems run code.
One lesson, every learner
Multilingual Learners
- Translation diagram.
- Frame: "code is translated into ___."
- Use a simple example.
Support & Access
- Start with "code must be translated."
- One difference.
- Use a visual.
Stretch & Extend
- Explain bytecode & the JVM.
- Compare compile vs run time.
- Time a compiled vs interpreted run.
What to gather
- 📽️Screen / board
- ⚙️Translation diagram
- 💻How Code Runs
- 📋Language sort sheet
- 📓Notebooks
- 🎫Exit-ticket slips
Key terms — hover for a quick definition
Exit Ticket
Preview the three formative checks. Tap “Sample answer” to see what mastery looks like — hide them before you print for students.
Reflect: how code runs.
Have students classify real languages as compiled or interpreted. A printable sort sheet is in the CS library.
Study the key terms
Tap a card to flip it, then rate whether you knew it. Built from this lesson’s vocabulary.
Nice work!
Check your understanding
A quick self-check with instant feedback, drawn from this lesson’s key terms.
Nice work!
Printable worksheet
A print-and-go review sheet with a built-in answer key. Tap “Show answer key” to reveal answers, or print the clean version for students.
Part A · Write the word that matches each meaning
- translates all code first
- while the program runs
- the code you write
- convert to machine code
- hiding lower-level detail
- run the program
- instructions the CPU runs
- runs code line by line
Part B · Show what you learned
- Why must source code be translated?
- What does a compiler do?
- What does an interpreter do?
Part B: 1) The computer only runs machine code. 2) Translates the whole program into machine code before it runs. 3) Runs the code line by line, translating as it goes.