Skip to main content
โ† Back to Traditional Coding samples
โŒจ๏ธTraditional Codingยท15 minยทSample Lesson

First Steps in Traditional Coding

Did you know that before a computer can do ANYTHING, someone has to tell it every single step -- in exact order? Even something as simple as 'make a peanut butter sandwich' has to be broken into tiny steps for a computer: open the jar, pick up the knife, scoop the peanut butter, spread it on the bread. That's exactly what coding is: giving a computer clear, ordered steps called instructions!

What You'll Learn

- What a computer program really is - Why the ORDER of steps matters so much - What a 'bug' is and how coders fix them - How to give step-by-step instructions like a real coder

A Program Is Just a List of Steps

A computer program is a list of instructions, written in order, that tells a computer exactly what to do. Coders use special typed words (called code) instead of regular sentences, because computers need instructions to be exact -- they can't guess what you meant. If you wanted a robot to draw a square, you couldn't just say 'draw a square.' You'd have to say: move forward 4 steps, turn right, move forward 4 steps, turn right, move forward 4 steps, turn right, move forward 4 steps, turn right. That's four repeated instructions -- and coders have a special name for repeating steps like this: a loop!

Order Matters -- A Lot

Imagine you told a friend to 'put on your shoes' and then 'put on your socks' -- shoes first would feel silly and uncomfortable! Computers are the same way: if the steps are in the wrong order, the program won't work right, even if every single step is correct on its own. This is one of the very first rules real coders learn: a computer will do EXACTLY what you type, in EXACTLY the order you typed it, even if that's not what you meant.

What's a Bug?

When a program doesn't work the way it's supposed to, coders call the mistake a 'bug.' Finding and fixing a bug is called 'debugging.' Even the best coders in the world get bugs in their code all the time -- it's a normal part of coding, not a failure!

Practicing Like a Real Coder

Real coders test their instructions by running them and watching what happens, then fixing anything that went wrong. You can practice this exact skill without a computer at all -- by writing step-by-step instructions for a simple task, like getting a glass of water, and having someone follow your instructions EXACTLY as written (even if it looks silly). If they mess up, that's not their fault -- it means your instructions had a bug!

Match each coding word to what it means.

Terms

Program
Bug
Loop
Debugging

Definitions

A mistake that makes a program not work
Repeating the same steps
A list of instructions for a computer
Finding and fixing a mistake

Drag terms onto their definitions, or click a term then click a definition to match.

โ“

Why does the ORDER of steps matter in a computer program?

โ“

What do coders call a mistake that makes a program behave incorrectly?

๐ŸŽฏ

Write a Silly Instruction List

Write 5 numbered steps telling someone exactly how to make a peanut butter sandwich, being as exact as possible (example: '1. Pick up the bread bag with one hand'). Give your list to a family member and have them follow ONLY what is written, even if it looks silly. Watch where the instructions break down, then fix your list to remove the bug.

Want to keep learning?

Sign up for free to access the full curriculum โ€” all subjects, all ages.

Start Learning Free
First Steps in Traditional Coding | Free Sample | HYVE CARES | HYVE CARES