What Is a Program, Really?

Before we write a single line of Java, let us be honest about what a program is. Once that is clear, the syntax we are about to learn will feel like a small detail by comparison.

A program is a precise plan

A program is a precise, unambiguous plan for what a machine should do. That is the whole definition. Recipes, knitting patterns, sheet music, and tax forms are all "programs" in this larger sense. What makes computer programs special is just two things:

1. They are written in a language a machine can understand exactly, with no room for interpretation.
2. The machine can execute them fast — billions of operations per second.

Everything else — variables, classes, lambdas, design patterns — is just a way of writing those instructions more clearly.

Inputs, processing, output

Almost every program, at the largest scale, looks like this:

• Input. Where does the data come from? The keyboard, a file, the network, a sensor, another program.
• Processing. What is done with the data? Calculation, rearrangement, filtering, comparison.
• Output. Where does the result go? A screen, a printer, a file, the network, a robot arm.

When you stare at a complicated piece of software and feel lost, it often helps to ask: what is the input? what is the output? what is the processing in between? Almost any program will yield to those three questions.

A first program — annotated

Here is a tiny Java program. Read it the way you would read a recipe.

Things to notice, without yet worrying about why Java looks the way it does:

• The instructions run top to bottom, one after another. By default, that is always how a program works.
• int a = 7; is not a math equation. It is a command. It says: "create a small box called a, and put the number 7 inside it."
• System.out.println(...) is a command that says "print the following to the output."

Imperative vs declarative

Most of what we write in this course is imperative: a sequence of commands that change the state of the program. Do this, then that.

There is another style, called declarative, where you describe what you want and the system figures out how. SQL is declarative ("give me all customers from France"); HTML is declarative ("a heading saying 'Hello' goes here"). Even within Java, the modern stream API is somewhat declarative.

Both styles eventually become imperative at the bottom — somebody has to write the actual instructions a CPU executes — but it is useful to know that "programming" is not just one mental model. When we get to OOP later, we will mix imperative method bodies with a declarative structure of classes and interfaces.

What programs cannot do

Programs are powerful, but they are not magic. Two limitations are worth remembering forever:

1. A program does exactly what it says, not what you meant. If you tell it to multiply when you meant to add, it will multiply, faithfully, until you fix it.
2. A program can only act on information it has. If you do not give it the data, it cannot guess.

Both of these limitations are also opportunities. They are why programs are predictable, and that predictability is the foundation of every computational system in the world.

"Hello World" as a milestone

When you successfully run your first program — usually one that prints "Hello World" — something subtle happens in your head. You realize that you, personally, can now make a machine do something on purpose. That is a small but real superpower. You don't lose it.

Try this:

There it is. You made a computer talk.

A small challenge

Let's stretch slightly. Modify the program below so it prints these three lines, exactly:

Hello, Ada!
Hello, Grace!
Hello, Linus!

Hello, Ada!
Hello, Grace!
Hello, Linus!

You did it. You instructed a machine. The rest of the course is about doing this with more and more sophistication.