How a Computer Thinks 🧠

A very fast machine that only does simple things

Here is the whole secret of computing: a computer is not smart. It performs only tiny, dumb operations (add two numbers, copy a value, compare, jump to another instruction), but it performs billions of them per second, perfectly, without getting bored. Everything you have ever seen a computer do, from Netflix to spreadsheets to this website, is built from those tiny steps stacked very, very high.

Programming is the art of writing those steps down. You are not summoning magic. You are writing an extremely precise recipe for an extremely fast, extremely literal cook.

The kitchen: CPU, memory, and storage 🍳

Think of the computer as a restaurant kitchen:

• The CPU is the chef. It reads one instruction at a time and executes it, incredibly fast. Modern chips have several chefs working side by side (called cores). Remember that for Lesson 16, where Rust lets you use them all safely.
• RAM (memory) is the countertop. Fast to reach, but small, and it gets wiped clean when the power goes off. Running programs keep their working data here. When Rust talks about "the stack" and "the heap" in Lesson 6, it means two regions of this countertop.
• The disk is the pantry. Huge and permanent, but slower to reach. Your files live here, including the program files themselves.

A "program" at rest is just a file in the pantry. Running it means the chef starts reading its instructions and using counter space for its ingredients. When Lesson 6 says memory must be given back, this countertop is the thing being managed.

Binary: why ones and zeros?

Deep down, a computer stores everything as electrical switches that are either on or off. Write on as 1 and off as 0 and you get binary. With enough switches you can encode anything: the number 42 is 101010, the letter A is 01000001, and a photo is millions of such patterns describing pixel colors.

You will almost never work in binary. But it explains vocabulary you will meet constantly: a bit is one switch, a byte is eight of them, and the number types you will meet in Lesson 3 (i32, u8) are literally named for how many switches they occupy. An i32 is a number stored in 32 switches. That is the whole mystery.

From your words to the chef's language

The chef speaks only machine code: raw numeric instructions. Humans are terrible at writing it directly, so we invented programming languages, which are human-readable notations that get translated for the chef. There are two big translation styles:

Rust is compiled. That is why the workflow you will learn is write, compile, run, and why the compiler (rustc) gets to inspect your whole program and refuse it if something is unsafe. A strict translator is annoying for five minutes and priceless for five years.

What an operating system does

One more character: the operating system (macOS, Windows, Linux) is the kitchen manager. It decides which programs get CPU time, hands out memory, guards files, and provides services every program needs (drawing windows, reaching the network, reading the keyboard). When your Rust program prints text or opens a file, it is politely asking the OS to do it. The web server you will run in this course asks the OS for a "port" to listen on. Same idea.