Computational Thinking

Abstraction

Leaving out the details that don't matter so the problem gets easier.

What's really going on

Real problems come with more detail than anyone can handle at once. Abstraction means keeping only the details that matter for the job and leaving out the rest. A subway map is a good example: it skips the streets and buildings and shows only the stops and how they connect, which is exactly what a rider needs. Programmers do the same thing when they write a function that you can use without knowing how it works inside.

For educators

Background

Abstraction is one of the core practices of computational thinking, alongside decomposition, pattern recognition, and algorithms. It works in two directions: leaving out detail to model a problem (a graph instead of a street map), and hiding detail behind a name so it can be reused (a function, a library, an icon). Students already use abstractions all day, so the teaching move is to make them notice the choice of what to keep and what to drop, and that the right choice depends on the problem.

Misconceptions

  • Abstraction means making something vague or less accurate. A good abstraction is precise about the details that matter; it only drops the ones that don’t.
  • There is one correct abstraction of a problem. Different goals call for different models: a tourist map and a plumbing diagram of the same building keep different details.
  • Abstraction is only about code. Maps, diagrams, recipes, and models in every subject are abstractions.