What Code Is

Every app on your phone, every website you open, every game you've played — each one is, underneath, a long list of written instructions. Someone sat down and wrote out, step by step, everything the computer should do. That list of instructions is called code, and this topic is about what it actually is.

The surprise for most people is how ordinary it looks. Code isn't a wall of glowing symbols or secret math. It's text — words and punctuation a person typed and saved in a file, much like the text in a document. The difference is what the text is for: it tells a computer exactly what to do.

Ideawhat should happen

→

Written codeexact steps, as text

→

Computer follows itexactly, step by step

What is code, really?

Code is a set of instructions that tells a computer what to do, written as precise steps in an order. Each line is one small command — show this text, add these two numbers, wait for a click — and the computer does them one after another, top to bottom.

That ordered, step-by-step nature is the heart of it. A computer doesn't take in a whole idea at once and figure out the rest. It needs every step spelled out and arranged in sequence, because it will do them in exactly that sequence and nothing more.

This connects straight back to the earlier topics on the processor. The CPU follows instructions one tiny step at a time; code is where those instructions come from. Writing code is writing the steps the machine will carry out.

It's just text that people write

Code is written by people, typed out like any other text, and saved in ordinary files. Those files are often called source code, or just the source — the original human-written version that everything else is built from. You'll meet that word again in this chapter and in the Git course.

Because it's plain text, code can be read, copied, and edited the same way you'd edit a document. There's nothing magical inside the file. Open one and you'd see lines of words, names, and punctuation — unfamiliar at first, but plainly text someone typed, not a sealed mystery.

Computers are painfully literal

Here is the part that trips up almost everyone new to this: a computer does exactly what the code says, not what the person meant. It has no common sense and never guesses your intent. If the instructions say something slightly wrong, the computer carries out the wrong thing without hesitation.

Think of code as a recipe handed to a cook with zero common sense, who follows it to the letter. The recipe says "add salt" but never says how much, so the cook stops, confused — or dumps in the whole box. A human cook would just use a pinch. The computer is that literal cook: it does precisely what's written, including the gaps and the mistakes.

That's also why a mistake in code is called a bug — an instruction that tells the computer to do the wrong thing, which it then dutifully does. The computer isn't broken when there's a bug; it's faithfully following a flawed instruction. "Bug" is another word you'll see in nearly every course that follows.

A tiny taste of what it looks like

You won't write any code in this course, but it helps to see a few lines so the word stops being abstract. Imagine three instructions, in order: ask the person for their name; store whatever they type; then show the message "Hello," followed by that name.

Real code says almost exactly that, just with stricter wording and punctuation so there's no room for ambiguity. The ideas are readable — ask, store, show — but every detail has to be exact, because the literal machine will follow each step precisely as written and not one bit more.