Learn to code,
one clear step at a time.

A program is a list of instructions that a computer follows, one after the other, exactly as written. Programming (also called coding) is the act of writing those instructions in a language both you and the computer can understand.

That is the whole secret. Your phone does not "think" — it simply obeys. If the instructions are in the right order and the right format, you get the right result. If not, you get a bug.

The five things every program does

• 1
  Input — take data in. A keyboard press, a file, a button tap, or a number you typed.
• 2
  Store — keep that data somewhere with a name, so you can use it later. These named boxes are called variables.
• 3
  Process — do maths, compare values, join text together, or make decisions.
• 4
  Repeat — do the same job many times without writing it many times. That is a loop.
• 5
  Output — show the result. Print it on screen, save it to a file, send it over the internet.

Programming is younger than you think, and it was invented by people who were told it was not their field. Knowing this history makes the modern tools make sense.

The five generations of languages

• 1
  1st — machine code. Pure 0s and 1s. Humans wrote these by hand on paper first.
• 2
  2nd — assembly. Short codes like MOV and ADD instead of numbers. Still one line per CPU instruction.
• 3
  3rd — high-level. C, C++, Python, Java. You write total = price * qty and the compiler worries about the machine.
• 4
  4th — declarative. SQL and spreadsheets: you describe the result, not the steps.
• 5
  5th — logic and AI. You describe the problem and constraints, and the system works out the solution.

The CPU only understands its own machine code — numbers. So your file has to be translated first. There are two ways, and every language chooses one.

• 1
  JIT (just-in-time) is a middle path — JavaScript engines translate the hot parts while running, giving both speed and instant testing.
• 2
  A compiler error means the program never starts. An interpreter error means it ran until it hit the bad line — everything before that already happened.
• 3
  This is why Python is easier for your first week: no build step between you and a result.

Three honest rules

• 1
  The best first language is the one that lets you finish something. A finished small project teaches more than three unfinished big ones.
• 2
  Do not start two languages in the same month. The syntax will blur and every beginner hits this.
• 3
  After your first language, the second takes about two weeks — because you are only learning new spelling, not new thinking.

• 1
  Week 1–2 · Setup and first programs. Install the tools, print text, take input, do maths, and store values in variables.
• 2
  Week 3–4 · Decide and repeat. if/else, while, for. Build a marks calculator and a multiplication-table printer.
• 3
  Week 5–6 · Break the problem up. Functions, and lists or arrays. Build a quiz game that scores the player.
• 4
  Week 7–8 · Store things. Dictionaries, objects, files, and your first SQL query.
• 5
  Week 9–10 · Ship something. One finished small project — a to-do list, a notes app, a report generator.
• 6
  Week 11–12 · Read other people's code. Then rewrite your project a second time. The rewrite is where it clicks.

The daily habit that decides everything

• 1
  15 focused minutes a day beats a four-hour Sunday. Memory needs repetition, not marathons.
• 2
  Type every example by hand once. Copy-paste feels faster and teaches almost nothing.
• 3
  Keep an errors.md file. When a bug takes more than ten minutes, write down the fix. Your own notes will out-teach any tutorial.
• 4
  Getting stuck is not a sign you cannot do this. It is the actual job — experienced developers spend most of their day stuck on smaller problems.

questions = [
    ("What does CPU stand for?", "central processing unit"),
    ("Which symbol starts a comment in Python?", "#"),
    ("What is 7 // 2 in Python?", "3"),
]

score = 0
for prompt, answer in questions:
    guess = input(prompt + " ").strip().lower()
    if guess == answer:
        score += 1
        print("Correct!")
    else:
        print(f"Not quite - the answer is {answer}")

print(f"\nYou scored {score} out of {len(questions)}")

How to get unstuck, in order

• 1
  Read the error message properly, bottom to top. It names the file, the line and the type of problem.
• 2
  Print your variables right before the failing line. Guessing is slower than printing.
• 3
  Shrink the problem. Comment out half the code. If it works, the bug is in the other half.
• 4
  Change one thing at a time. Changing three things and hoping is how hours disappear.
• 5
  Say it out loud. Explaining the problem to anyone (or to a rubber duck) finds a surprising number of bugs by itself.
• 6
  Then ask. Include what you expected, what actually happened, and the smallest code that shows it.