Code, Tools, and History

Overview

Students explore how computers developed, learn essential computing vocabulary, and complete a beginner coding activity in Code.org. They will practice choosing appropriate digital tools, following algorithms, and explaining how technology supports problem solving.

Learning intentions

Students will be able to:

• Define common computer and coding terms.
• Describe two important developments in computer history.
• Use Code.org to create and test a simple block-based program.
• Explain how coding tools help users solve problems.

Success criteria

• I can correctly use at least six computer or coding terms.
• I can place two computer-history events in reasonable chronological order.
• I can create, run, and revise a Code.org program.
• I can explain what an algorithm, bug, and block do.

Curriculum links

• Mathematical Practice: Consider available tools strategically, recognizing their uses and limitations.
• Writing in Technology: Conduct a short research task using several provided sources or information points.
• Writing in Technology: Use technology to produce and present information clearly and efficiently.

Lesson structure (36 minutes)

1. 0–4 min · Hook and prior knowledge. Teacher opens with the opening question and computer-history image and asks, “How can a device that fits in your hand do more than an early computer that filled a room?” Students make a quick prediction and share one computer-related word they already know.

2. 4–10 min · Vocabulary and history mini-lesson. Teacher uses the vocabulary and timeline slides to introduce hardware, software, input, output, algorithm, program, block, sequence, loop, and bug, then presents a short timeline from room-sized early computers to personal computers, smartphones, and cloud computing. Students complete the matching and timeline prompts on the computer vocabulary and history worksheet.

Suggested questions and answers:

• What is hardware? The physical equipment we can touch, such as a keyboard or screen.
• What is software? Instructions or programs that tell hardware what to do.
• What is an algorithm? A clear, ordered set of steps for solving a problem.
• What is a bug? An error in a program that causes an unexpected result.
• What is input? Information entered into a computer, such as a key press.
• What is output? Information a computer produces, such as sound or an image.
• Why are coding blocks useful for beginners? They reduce typing errors and make program structure easier to see.

3. 10–14 min · Teacher modeling. Teacher projects the Code.org workspace using the Code.org workspace and block-coding demonstration. Model dragging a block into the workspace, running the program, observing the result, and changing the sequence. Students identify the input, output, algorithm, and possible bug in the example.

4. 14–27 min · Hands-on coding challenge. Teacher directs students to open the assigned beginner Code.org activity and displays the coding challenge instruction slide. Students work individually or with a partner to complete the first available sequence-based puzzles, run their code after each change, and record one successful instruction sequence and one correction on the coding practice recording section. Circulate and ask, “What do you predict will happen before you run it?” and “Which block or sequence caused the problem?”

5. 27–32 min · Debug and explain. Teacher pauses the class and presents a deliberately incorrect program from the debugging discussion slide. Students use their screens or worksheet to identify the bug, explain the expected output, and suggest a correction. Invite two students to explain different solutions and discuss whether both are efficient.

6. 32–36 min · Review and exit check. Teacher uses the review and exit-question slide to revisit the learning intentions. Students complete the final questions on the exit check section: define algorithm and bug, name one hardware item and one software example, and describe one change they made to improve their program. Collect worksheets as students leave.

Resources

• Computers or tablets with reliable access to the assigned Code.org beginner activity
• Teacher computer and projector
• the complete code, vocabulary, and history slide deck
• the computer vocabulary, history, coding practice, and exit-check worksheet
• Student headphones, if available
• Whiteboard and markers
• Prepared incorrect code example for debugging
• Student login information or preassigned activity directions

Assessment

• During vocabulary instruction, check worksheet responses and ask students to use terms in complete explanations.
• During coding, circulate with a checklist: student creates a sequence, runs the program, observes the result, and revises a bug.
• Use the worksheet exit check to identify students needing further support with vocabulary, sequencing, or debugging.

Differentiation

• Provide a word bank, illustrated vocabulary prompts, and sentence starters such as “The bug is ___ because ___” and “The program outputs ___.”
• Pair students strategically; assign a navigator who predicts and explains and a driver who controls the computer, then switch roles halfway through.
• For students needing additional support, pre-open the Code.org activity, reduce the number of puzzles, and model one puzzle step by step.
• Challenge early finishers to solve a puzzle in two different ways and compare which algorithm uses fewer blocks or is easier to understand.
• Support English learners with visual demonstrations, gestures, partner rehearsal, and permission to record ideas using labeled diagrams before writing sentences.
• Follow student IEP or 504 accommodations, including extended processing time, enlarged text, alternative input devices, or adult assistance as needed.