Unit 8 — Coding and Computer Science - Hour of Code and Block Coding

• Observation of students completing coding challenges
• Discussion of what code does and why it works
• Debugging and problem-solving during coding activities
• Attempts and iterations on coding puzzles

Completion of Hour of Code or Sphero challenge demonstrating understanding of sequencing and logical thinking; ability to modify code to achieve different outcomes

— not configured —

Students may demonstrate understanding through teacher-guided coding activities with simplified block sequences, verbal explanation of what their code does, or direct manipulation of physical objects to show sequencing concepts. Visual supports such as step-by-step picture guides or pre-built code blocks may be provided.

Students may benefit from visual step-by-step supports that break coding sequences into smaller, numbered chunks, helping them track their place in a program without holding too many steps in working memory. Provide simplified block menus with fewer choices at a time so students can focus on one concept — such as sequencing before introducing loops. Allow oral explanation of what their code does as an alternative or supplement to written reflection, and offer additional think-time and adult check-ins during debugging tasks. Pairing physical, unplugged movement activities that mirror on-screen sequences can reinforce computational thinking for students who need kinesthetic entry points.

Students should have access to a distraction-reduced workspace during independent coding challenges, as sustained screen-based focus can be difficult in an open environment. Extended time on challenge completions and check-in moments between coding tasks help ensure students can demonstrate understanding without fatigue becoming a barrier. Preferential seating near the teacher during direct instruction on new concepts such as loops or conditionals supports attention and quick access to re-explanation.

Introduce and pre-teach key vocabulary — such as sequence, loop, command, debug, and condition — using visual icons or diagrams that pair the word with a concrete image or action before students encounter it in a coding context. Directions for coding tasks should be given in short, clear steps with visual models of expected inputs and outputs so students can follow along without relying solely on English language processing. Where possible, allow students to discuss their coding logic with a partner who shares their home language, and use on-screen visual feedback from the program to help them self-check meaning.

Begin with the most concrete, visual coding puzzles available and allow students to work through foundational sequencing concepts with a partner before attempting challenges independently, so prior success builds confidence for more complex tasks. Reduce the number of required steps or blocks in a given challenge so students experience completion and can identify cause-and-effect relationships in their code before adding complexity. Connect the idea of debugging to familiar everyday experiences — like retracing steps when something goes wrong — to activate prior knowledge and make the problem-solving process feel approachable rather than frustrating.

Students who quickly grasp sequencing and loops should be encouraged to explore how combining multiple concepts — such as nested loops or conditional logic — can make their code more efficient, moving toward elegant rather than just functional solutions. Challenge these students to reverse-engineer a working program to explain why it works and then modify it intentionally to produce a different outcome, building deeper analytical thinking about computational logic. Opportunities to serve as peer debugging consultants or to design their own open-ended Sphero challenge for classmates can extend learning into creative design and communication of technical thinking.