Imagine a friend rings you up and asks, "How do I walk from the station to your house?" You would not describe every brick in every wall, the colour of each front door, or how many leaves are on the trees. You'd say something like: "Turn left, go past the shop, then it's the third house on the right."

Without even thinking about it, you just did something clever. You threw away the thousands of details that don't matter and kept only the few that do. That is abstraction:

It's one of the most powerful ideas in all of computing — because computers deal with enormous, complicated things, and the only way our brains can cope is to hide most of the mess and look at just the part we care about right now.

A map is abstraction you can hold in your hand

A street map is a brilliant example. The real world is packed with detail: pavements, lamp-posts, parked cars, gardens, the smell of the bakery. A map hides almost all of it and keeps just the roads and their names — because that is all you need to plan a journey. If a map showed every single thing, it would be as big and confusing as the real world, and utterly useless.

The famous London Underground map takes this even further. It is not geographically accurate at all — the stations aren't really where the map puts them, and the lines aren't really straight. Harry Beck redrew it in 1931 as neat straight lines and even spacing. Geographically it's "wrong", but for the one job it's built for — which train do I get, and where do I change? — it is absolutely perfect. He hid the true distances (a detail you don't need underground) and kept the connections (the detail you do).

Detailed picture, or the icon you actually use?

Here are two ways to show the same neighbourhood. On the left is the real place, crammed with buildings, trees and winding lanes. On the right is the map — the same place with almost everything hidden, leaving just the roads and stops you need to find your way. Step through it and watch the clutter fall away.

Notice: the map isn't "less true" in a way that matters — it's more useful, because it answers the question "how do I get there?" without drowning you in things that have nothing to do with that question.

Abstraction in code: use it without knowing how it works

Programmers lean on abstraction all the time. Suppose you want the average of some test scores. Someone can write a function called \text{average(scores)}. Once it exists, everyone else can just use its name — they never have to know, or even care, how it works inside. The name hides the machinery.

The person calling \text{average} only needs to know three things: its name, what to put in (a list of scores), and what comes out (the average). The loop, the running total, the dividing — all of that is hidden behind the name. In fact, someone could rewrite the insides completely and, as long as it still returns the average, none of the code that uses it would need to change at all.

This is why abstraction lets us build huge programs: each piece hides its own complicated insides behind a simple name, so you can snap the pieces together like bricks without holding every detail in your head at once.