Instructions and Order: The Traffic Signal Imagine you are standing at a road crossing. There is a traffic signal with three lights: red, yellow, and green. You already know what each light means. Red means stop. Yellow means get ready. Green means go. Now here is a question: what would happen if the lights came on in the wrong order ? What if it went green, then red, then yellow, instead of red, yellow, green? Chaos. Accidents. Nobody would know whether to stop or go. The order of the signals is not just a detail — it is the whole point. And this is one of the most important ideas in programming. Computers Follow Instructions in Order When you give a computer a set of instructions, it does them one at a time, in exactly the order you wrote them. It does not skip steps. It does not do step 3 before step 2. It does not guess what you meant. It follows the list, from top to bottom, one step at a time. This is called a sequence . A sequence is a list of instructions that must be followed in a specific order to get the right result. The Traffic Signal as a Sequence A real traffic signal runs a sequence that looks something like this: 1. Turn on the Red light — wait 30 seconds 2. Turn on the Yellow light — wait 3 seconds 3. Turn on the Green light — wait 25 seconds 4. Turn on the Yellow light again — wait 3 seconds 5. Go back to step 1 If a computer is controlling this signal, it follows these steps in exactly this order. Not because it understands traffic. Not because it is smart. Simply because someone wrote the steps in that order, and the computer follows them. Why Order Matters So Much Let's say a cook wants to make tea: Correct sequence: 1. Boil water 2. Pour water into the cup 3. Add the tea bag 4. Wait 2 minutes 5. Remove the tea bag and serve Wrong sequence: 1. Add the tea bag 2. Pour cold water into the cup 3. Boil water You will not get tea. The steps are all there — but the order is wrong. A computer has the same problem. Give it the right instructions in the wrong order, and the result will be wrong. Or nothing will work at all. Instructions Must Be Clear There is another thing about computer instructions: they must be very exact. A traffic signal does not understand "turn on the light soon." It needs to know: Which light? (Red, Yellow, or Green) When exactly? (After how many seconds?) For how long? Computers do not understand vague instructions like "soon" or "a bit" or "later." Every instruction must say exactly what to do. This is different from talking to a friend. If you tell a friend "wait a bit," they know what you mean. A computer will be confused — because "a bit" could mean 1 second or 1 hour. Sequence is the Foundation Almost everything in programming starts with a sequence — an ordered list of clear, exact steps. You will later learn how to make a computer take different paths depending on a situation (called decisions ), or repeat a set of steps many times (called loops ). But both of those ideas are built on top of sequences. The traffic signal does all three — and we will get there. For now, remember: computers follow instructions in order, one step at a time, and the order matters completely. ✅ Summary A sequence is an ordered list of clear, exact steps. Computers follow sequences from top to bottom, one step at a time. The traffic signal is a perfect example — it works correctly only because the lights come on in the right order. Change the order, or make the instructions unclear, and nothing works as expected. Sequence is the first and most important idea in programming.