Logic Loops Slides STEM: Level 1
Logic
Loops
Mastering the language of machines through sequencing and patterns.
The Secret Recipe
An algorithm is a step-by-step set of instructions to complete a task.
Examples:
• Tying your shoes
• Making a peanut butter sandwich
• Solving a Rubik's Cube
• Following a LEGO manual
Think of it like a recipe for a computer!
Step by Step
Computers are fast, but they aren't very smart. They do exactly what you tell them, in the order you say it.
1
Put on Socks
2
Put on Shoes
3
Tie Laces
4
Walk Outside
What happens if we swap Step 1 and Step 2? Chaos!
The Power of Loops
Don't work harder, work smarter! A loop tells a computer to repeat a set of instructions.
// The Efficient Way
Repeat (5 times) {
Loops save time and keep your code clean!
Time to Code
https://hourofcode.com/learn
Choose your quest on Hour of Code or Scratch !
Minecraft
Solve puzzles with blocks
Dance Party
Code a musical sequence
Star Wars
Navigate the galaxy
Follow the instructions and see your code come to life!
Logic Loops Teacher Guide Logic Loops
Teacher Facilitation Guide
Duration
60-90 Min
Learning Objectives
Define and identify algorithms in everyday life.
Execute and create precise sequences for a specific task.
Apply loops to optimize repetitive sequences in code.
Navigate online coding environments to solve basic logic puzzles.
Materials Needed
Physical
• Logic Loops Handouts
• Pencils & Erasers
• LEGO or building blocks
Digital
• Logic Loops Slides
• Laptops/Tablets
• Hour of Code / Scratch Access
Essential Questions
"How do computers understand the world?"
"Why is the order of instructions critical in programming?"
"How can we make code more efficient?"
Instructional Sequence
00-10 Min
Hook: The Sandwich Algorithm
Ask students to write instructions for making a sandwich. Follow a student's literal instructions (e.g., if they say "put jam on bread," put the whole jar on the loaf) to demonstrate the need for precision.
10-25 Min
Direct Instruction
Use the Logic Loops Slides to introduce Algorithms, Sequencing, and Loops. Use the "Sock and Shoe" analogy to reinforce sequence importance.
25-45 Min
Offline Practice
Distribute the Logic Loops Handout . Students practice writing pseudo-code and identifying loops in "Robot Run" logic puzzles.
45-80 Min
Online Exploration
Students log into Hour of Code (Dance Party or Minecraft themes) to apply their knowledge in a block-based coding environment.
Common Misconceptions
The "Smart" Computer
Students often think computers can "guess" what they mean. Emphasize that computers are literal and require absolute clarity.
Infinite Loops
Students may forget to define an "end state" for a loop. Explain that a loop needs to know exactly when to stop repeating.
Differentiation
Support
Provide "Command Cards" (physical arrows and icons) for students to arrange before writing them down.
Extension
Challenge students to create "Nested Loops" (a loop inside a loop) for complex patterns like drawing a square 4 times.
Discussion Prompts
1
Can you think of a loop you perform every morning while getting ready?
2
If you were teaching a robot to brush its teeth, what is the very first step?
3
Why might a programmer use a loop instead of writing the same command 100 times?
4
What happens to an algorithm if one step is missing or out of order?
Digital Architects Sequence • Lesson 1
© 2026 STEM Education Lab
Logic Loops Handout Logic Loops
Student Mission: Offline Coding
Agent Name
Date
Task 1: The Daily Algorithm
Computers need exact steps. Write an 8-step algorithm for a simple task: Brushing Your Teeth. Be as literal as possible!
01
05
02
06
03
07
04
08
Task 2: Robot Run
MAP-01
The Grid Map
Path
Wall
Goal
Code WITHOUT Loops
How many steps to reach the star?
Code WITH Loops
Optimize your code! Use a loop for the long straight sections.
REPEAT
TIMES {
} END REPEAT
Task 3: The Pattern Maker
Programmers love efficiency. Below is a repetitive code sequence. Write a single loop that does the same job.
Inefficient Code
Move Forward
Clap Hands
Move Forward
Clap Hands
Move Forward
Clap Hands
Move Forward
Clap Hands
Your Loop Code
REPEAT
TIMES {
}
Mission Reflection
In your own words, why do programmers use loops instead of writing every step individually?
Digital Architects // Lesson 01 Code-101-Worksheet
Bridge Blitz Slides Phase 2: Engineering
Bridge
Blitz
Build. Test. Break. Repeat.
The Design Cycle
Engineering isn't about getting it right the first time. It's about a process .
1. Ask
What's the problem?
2. Imagine
Brainstorm ideas!
3. Plan
Sketch your design.
4. Create
Build your prototype.
Step 5: Improve
This is where the magic happens!
Battle of the Forces
Compression
A squeezing force. Imagine pushing a spring together. The top of your bridge is being squeezed!
Tension
A stretching force. Imagine pulling a rubber band. The bottom of your bridge is being pulled apart!
Balance these forces to win the challenge!
Structural Secrets
Why are bridges full of triangles? Because triangles are the strongest shape in engineering!
Squares can collapse into parallelograms.
Triangles distribute weight evenly to all sides.
Weak Shape:
Strong Shape:
Mission Briefing
1. Goal
Build a bridge that spans 12 inches and holds the most weight (books or weights).
2. Materials
• 50 Popsicle Sticks
• 1 Roll of Tape
• 12" Distance
3. Rule
No tape can touch the desk! Your bridge must stand on its own.
Get Building!
Bridge Blitz Worksheet Bridge Blitz
Structural Engineering Blueprint
Chief Engineer
Phase 1: Initial Blueprint
Sketch your bridge design below. Use triangles for strength. Label where you think Compression and Tension will happen.
Scale: 1 Square = 1 Inch
Materials Checklist:
50 Popsicle Sticks
1 Meter of Tape
12-inch Span Markers
Key Question:
How will your design handle the weight in the center?
Phase 2: Stress Testing
Test Round Weight Added (Lbs/Books) Observations (What bowed? What snapped?) 01 02 Failure
Phase 3: Structural Improvement
Why did it fail?
Identify the Weak Point:
The "Blitz" Fix (New Plan):
Final Strength Score:
/
Max Units Held
Digital Architects // Lesson 02 Document: EDP-STRUCT-01
Bridge Blitz Teacher Guide Bridge Blitz
Teacher Facilitation Kit
Engineering Level
PHASE 02
Challenge Objective
Students will apply the Engineering Design Process to construct a free-standing bridge that spans a 12-inch gap and supports maximum static weight. They will focus on balancing the forces of compression and tension through the use of trusses (triangles).
Key Physics Concepts
Compression
The "squeeze" force on the top of the bridge. Sturdy popsicle sticks excel here.
Tension
The "pull" force on the bottom of the bridge. Tape or joints are often the failure point here.
Build Constraints
No tape may touch the desk or support surfaces.
Maximum of 50 popsicle sticks per team.
Bridge must span exactly 12 inches.
Pacing Guide
PLAN (15m)
Sketching and identifying trusses.
BUILD (30m)
Constructing the main truss and deck.
TEST (15m)
Static load testing with weights.
ITERATE (15m)
Reinforcing failure points.
The "Bridge Doctor" Troubleshooting
Symptom: The Wobble
Bridge tips over or twists when weight is added.
The Cure:
Check for lateral bracing. Are the two sides of the bridge connected at the top? Use "X" patterns between trusses.
Symptom: The Snap
A single popsicle stick breaks under a heavy load.
The Cure:
Double-up sticks in high-compression areas (the very top chord). Laminate two sticks together with tape.
Engineering Success Rubric
Criteria In Progress (1) Stable (2) Industrial (3) Structural Design Mostly squares; little use of triangles. Clear truss system using triangles. Complex bracing; triangles on all planes. Iterative Testing Abandoned design after first failure. Identified failure point and made 1 fix. Analyzed failure; significantly improved load. Collaboration One student did most of the build. Roles shared; both students contributed. Seamless teamwork; clear communication.
Digital Architects Sequence • Lesson 2: Bridge Blitz
Bot Blueprint Slides Capstone Project
Bot
Blueprint
The ultimate fusion of code and construction.
The Perfect Pair
Hardware
The physical body of the robot. The gears, the motors, the wheels, and the recycled materials you'll use today.
// If it breaks when you drop it, it's hardware.
Software
The instructions that tell the hardware what to do. The logic loops and algorithms you practiced in Lesson 1.
// If you can't touch it, it's software.
Mission Objective
Design a Helper Bot that solves a real-world problem.
Cleaning
Sweeps up small crumbs.
Delivery
Carries a small load.
Gardening
Waters a plant.
Anatomy of a Bot
Your bot needs two things on its blueprint:
1
A Physical Prototype
2
A Functional Pseudo-Code
// Brain Logic
REPEAT (until full) {
Launch Sequence
Gather your materials, sketch your vision, and program your creation.
Design • Build • Code
Bot Blueprint Project Guide Bot Blueprint
Final Capstone Project Guide
Lead Architect
1. Bot Identity
Bot Designation (Name):
Primary Function (Purpose):
2. Hardware Inventory
List the recycled materials you will use for the body, wheels, and tools.
3. Physical Blueprint (Hardware)
Top View / Side View
Software Logic
Write the Pseudo-code that controls your bot's primary function. Remember to use Loops for repetitive actions!
Main Function
REPEAT
TIMES {
// Step 1
// Step 2
// Step 3
} END REPEAT
// If bot encounters obstacle...
// Logic:
Project Reflection
How does the hardware (the body) help the software do its job?
If you had a real motor and computer brain, what's one thing your bot could do that it can't do now?
Patent Pending // Digital Architects Capstone
COMPLETED
Bot Blueprint Teacher Guide Capstone Phase
Bot Blueprint
Final Project Facilitator Guide
Total Duration
120-180 Min
The Final Challenge
This capstone synthesizes Lesson 1 (Coding Logic) and Lesson 2 (Engineering Construction) . Students must design a robot that uses a physical body (Hardware) to execute a logical task (Software).
Learning Synthesis
Coding Goal
Write pseudo-code using Loops and Sequences that accurately reflects the bot's physical motions.
Engineering Goal
Build a prototype from recycled materials that features structural stability and task-specific "tools".
Presentation Specs
Each team must present their "Bot Pitch" covering:
The Problem it Solves
Hardware Demonstration
Software Logic Walkthrough
Resource Management
Bot Body Materials
Cereal boxes, paper towel rolls, plastic bottles, yogurt cups.
Connectors
Duct tape, hot glue (teacher supervised), zip ties, pipe cleaners.
Logic Tools
Post-it notes for "logic blocks", markers for labeling bot parts.
Project Mastery Rubric
Mastery Area Emerging (1) Proficient (2) Architect (3) Hardware (Build) Bot is fragile; purpose is unclear. Stable build; clearly visible tools/parts. Innovative design; highly stable; creative parts. Software (Code) Sequence is missing steps or out of order. Correct sequence with at least one loop. Complex logic; efficient use of nested loops. Synthesis Code and build don't seem related. Code accurately describes bot's body motions. Bot and code are a seamless unit; "logic" is intuitive.
Level Up: Extension Ideas
A
Micro:bit Integration
Transition from pseudo-code to actual code by mounting a Micro:bit to the bot to control LED patterns or sensors.
B
Simple Circuits
Add a coin cell battery and an LED to the bot's "eyes" to introduce basic electrical engineering.
C
Peer Code Review
