What Is a Computer?

Every computer, even a huge one in a data centre, does the same three things. Something goes in. The machine does work on it. Something comes out. That pattern has a name: input, processing and output.

When you tap a letter on a keyboard, that tap is input. The machine figures out which letter you meant and draws it on the screen. The picture on the screen is output. You did not see the work in the middle, but it happened.

A traffic light is a computer too. A sensor or a timer sends input. The controller picks red, amber or green. The bulbs are output. None of this needs a keyboard. It still matches the same three-step shape.

If something follows a fixed set of rules quickly and never gets bored, it probably has a computer inside. Game consoles, microwaves, school ID scanners and the screen in a lift all count. The rules might be simple, like 'when the door closes, go up one floor', but something is still doing input, work and output.

People are not computers in this sense. You can change your mind, guess, or get tired. A computer does the same steps the same way every time until someone changes the program. That is why bugs are so annoying: the machine did exactly what it was told, and the tell was wrong.

Knowing this shape helps later. When you learn coding, you are writing the work step. When you use an app, you are giving input and reading output. The words change, the pattern does not.

A computer can do billions of simple steps in one second. That speed makes it look clever, but each step is tiny: add two numbers, compare two values, move one square on a grid. Big results come from doing many small steps in order.

That is why instructions matter. If step 4 is wrong, every step after it might be wrong too, even when the computer runs perfectly. Fixing a program means finding the wrong step, not blaming the machine.

The next topic starts there: writing a plan so clear that a robot, or a computer, cannot misunderstand it.