Everything you need before the bell rings
Learning Objectives
Students will be able to…
- ✓Use clear names.
- ✓Add useful comments.
- ✓Indent & structure.
- ✓Clean up code.
Why does it matter HOW your code looks, not just that it works?
Readable, or Messy?
Project this and sort each habit into Readable or Messy.
55 minutes, five moves
Tap any phase to open the teacher moves and student actions.
Hook — Code Is Read
Who reads your code weeks later — and can they understand it?
👩🏫 Teacher Moves
- Pose the question.
- Share ideas.
- Set the goal.
🎒 Student Actions
- Think.
- Share.
- Get ready.
Use — Readable Code
Students learn.
👩🏫 Teacher Moves
- Send students to Readable or Messy?
- Sort each habit.
- Note names & comments.
🎒 Student Actions
- Sort.
- Say.
- Note it.
Modify — Clean It
Students practice.
👩🏫 Teacher Moves
- Rename a vague variable.
- Add a comment.
- Fix the indentation.
🎒 Student Actions
- Rename.
- Comment.
- Indent.
Create — Create
Students apply.
👩🏫 Teacher Moves
- Clean up a messy snippet.
- Add clear names.
- Split into a function.
🎒 Student Actions
- Clean.
- Name.
- Split.
Reflect — Reflect
Students close.
👩🏫 Teacher Moves
- Name a readable-code habit.
- Name a messy one.
- Complete the exit ticket.
🎒 Student Actions
- Name one.
- Name one.
- 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.
Create readable, documented programs.
Refine code for clarity.
Document code for others.
Communicate clearly through artifacts.
One lesson, every learner
Multilingual Learners
- Readable/messy code cards.
- Frame: "a clear name is ___."
- Compare two snippets.
Support & Access
- Sort readable vs messy only.
- Use 4 habits.
- Use clear examples.
Stretch & Extend
- Write a style guide.
- Refactor a program.
- Peer-review for readability.
What to gather
- 📽️Screen / board
- ✨Code-habit cards
- 💻Readable or Messy?
- 📄Messy snippet
- 📓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: writing readable code.
Have students clean up a messy code snippet. A printable snippet 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
- an agreed style
- easy to update later
- a note in code for humans
- code that is easy to understand
- what you call a value
- clean up without changing behavior
- a named reusable block
- spacing that shows structure
Part B · Show what you learned
- Name a habit that makes code readable.
- Name a messy habit.
- Why does readability matter?
Part B: 1) Clear names, comments, consistent indentation, or functions. 2) Vague names, no comments, or random indentation. 3) Code is read far more often than written — by others and future-you.