Computer Science
Hiding a lower layer behind a name so you can print without driving pixels

Listen
Abstraction layers stack on top of each other: hardware, machine instructions, the operating system, the language runtime, and your own code. Each layer hides the details of the one below behind a stable interface, so calling print() lets you show text without controlling the display hardware yourself.
What you will learn
- Name abstraction as hiding a lower layer behind a contract
- Place hardware, OS, language, and your function in a stack
- Explain why a stable interface lets the layer below change without breaking the code above
Hey, I am Byte. Abstraction here is LAYERS. When you call print(), you do not drive the display hardware, talk to the operating system’s drivers, or pack bytes onto a wire. Each layer hides the one below behind a stable name.
A useful stack: hardware (wires and gates) → machine instructions → operating system → language runtime → your function. You work at one layer and trust the contract underneath.
For example, print("hi") asks the language runtime to write two characters. The runtime asks the operating system to send them to the screen, and the operating system and its drivers handle the display hardware. Your code only had to know one name. Picture stacked contracts.
Key words
- abstraction layer
- A level that hides the machinery below behind a stable name and contract.
- contract
- What a layer promises to the layer above, without exposing how it is done.
Check yourself
Think about it
Where in a system you use daily are you relying on an abstraction without knowing the layers beneath it?