Program Purpose and Function

Every program has a purpose: the reason it exists, the problem it's solving for someone. A step counter app's purpose is to help a person track how much they walk. But purpose lives at the level of people and goals, not code. Function is different: it's the literal, mechanical sequence of operations the code performs, instruction by instruction, with no regard for what anyone wanted. Two people can describe the same app correctly and sound like they're talking about different things, because one is describing purpose (what it's for, who uses it, why it matters) and the other is describing function (what each line actually does to variables and data).

To describe a step counter broadly, you'd say its purpose: it counts steps and shows progress toward a daily goal. To describe it statement by statement, you'd trace the function: a sensor event increments a step variable, the program compares that variable to a goal value, and it updates a display with the current count. Tracing function is mechanical. You follow each statement in order and track how values change, the same way you'd hand-simulate any calculation.

This distinction matters because it sets up the idea that a program's actual behavior is just its function running, whatever that turns out to be, even if it contradicts the purpose the programmer intended. That gap between intention and actual behavior is exactly where errors live, which is why the next step is naming the three kinds of error that cause function to drift from purpose.