What Programming Is

This chapter is about what programming is, at a level where the rest of the course can build on it.

Programming Is Precise Problem Solving

Programming is the activity of describing a process so precisely that a computer can carry it out. A computer does not understand goals the way people do. It follows instructions exactly, one step at a time.

This is what makes programming different from ordinary communication. In everyday life, if you say “make me a sandwich,” another person fills in missing details from experience. A computer does not. If the instructions are incomplete, contradictory, or out of order, the result is wrong or the program fails.

This has become slightly less obvious in the age of generative AI. An AI assistant may sometimes guess what you meant even when your request is vague. That does not remove the need for precision. It only shifts where the guesswork happens, and as you will see across the course, guesswork is not a substitute for understanding.

From Goals to Steps

Suppose the task is: ask the user for their name and greet them.

That sounds simple, but it already contains several smaller steps:

1. Ask the user for a value.
2. Store that value somewhere.
3. Build the greeting text.
4. Print the greeting.

This is called problem decomposition: turning a larger task into smaller parts that can be solved one at a time. Good programmers do this constantly. They do not jump directly from a broad description to a finished program. They first identify the pieces.

Decomposition is also one of the most useful tools when working with AI assistants. A vague request like “build me a study log” gives the assistant nothing to anchor on. The same task broken into “ask the user for one entry, store the entry, and print a summary at the end” is much easier to reason about, regardless of who or what is writing the code.

Hello, Python!

Order Matters

Programs run step by step. The order of those steps changes what the program does.

Consider the difference between these two programs:

print("Hello")
print("World")

and

print("World")
print("Hello")

Both are valid. They do different things. A large part of learning to program is learning to predict what a given sequence of instructions will actually produce.

Put the socks on
Put the shoes on
Start running

Syntax Is the Grammar of a Programming Language

Programming languages have rules about how programs must be written. These rules are called syntax. If a program breaks those rules, you will see a syntax error.

A missing parenthesis or a misspelled keyword can be enough to prevent the program from running. Even putting two print commands on the same line causes a syntax error. The following program is not valid:

print("Hello") print("World")

Syntax errors are normal. Beginners encounter them often, and experienced programmers do too. The important skill is not avoiding all mistakes. It is learning to read the feedback carefully and correct the problem systematically.

The editor below has a Python program with a syntax error — it is missing a closing parenthesis. Try running the program with the play button. Then read the error message. Then, fix the program and try running it again.

Much of learning programming is learning to read and understand error messages, as well as learning to read programs and predict what they will do. Spotting syntax errors and understanding what they mean is an important part of that process.

Step 1: Study programming
Step 2: ???
Step 3: Profit

From Thinking to Code

When programming, you are translating your ideas into a form that a computer can interpret. This takes practice. A starting point is to first think through the problem in plain language, and then write code that corresponds to that thinking. The more you practice this translation, the better you will get at it.

Throughout these materials, you will also see exercises where you are asked to write out the steps of a program in plain language, or to e.g. sort lines of plain-language explanations into a logical order.

In some cases, you will even directly see how the plain language explanations translate to code. Below is the first example of such an exercise.

Reading Before Writing

In this course, you will not only write code. You will also read code, explain code, trace code, and debug code. This is intentional.

Being able to read a short program and explain what it does is one of the strongest foundations for later programming skill. It also matters when you use AI tools. If an AI assistant suggests code, the question is not “Did the AI sound confident?” The real question is “What does this program do, and how do I know?”

You will return to this stance again in Reading Code You Didn’t Write at the end of this part.

Below is an example of an exercise that focuses on reading code. Try to reason through the program and come up with an explanation of what it does. The exercises is graded by an AI assistant that will give feedback and guide you towards an answer.

print("****")
print("*")
print("****")
print("*")
print("****")

A Useful Working Habit

Before writing code, it is worth answering a few questions: what is the program supposed to do, what information does it need, what smaller steps does the task contain, and in what order should those steps happen? If you can answer them clearly, writing the code becomes much easier. If you cannot, that is useful information too. It usually means the task needs another round of decomposition before any code is worth writing.

I am learning Python.

Check Your Understanding

1. In your own words, what does “problem decomposition” mean?
2. Give an example of two instructions whose meaning changes when the order is swapped.
3. Why is reading code an important skill, even for someone who already knows how to write code?