Abstraction, the Course's One Idea

Every unit of the course leaned on the same move — hide the machinery, expose the contract — and seeing abstraction as one idea wearing eleven costumes is the deepest version of the whole curriculum.

Count the costumes. The abstract data type (0095) hid the representation and exposed the operations — one contract, many structures. Layering (0065) stacked contracts into architecture. The hardware unit ran the ladder explicitly (0235): problem, algorithm, program, assembly, machine code, each rung a contract hiding the rung below, with the level of abstraction (0179) as the dial. The operating system was abstraction with a badge (0292): applications ask, never touch — and virtual memory (0313) handed every process a private map that physical memory never promised. The languages unit sold abstraction as its founding product (0351): hardware complexity traded away so humans solve problems. The database unit abstracted twice — the data model over the storage (0414), the declarative query over the how (0423). The cloud stacked the final rungs (0559): infrastructure, platform, software, each service model a thicker contract over someone else's machinery, until serverless hid the servers themselves. Even the security unit spoke it: HTTPS wrapping the wire so the conversation needn't know the listeners. One idea, every altitude — and one honest cost, taught each time: an abstraction hides machinery from you too. The overflow that surprised the ledger (0196), the cache that sped code nobody rewrote (0258), the orchestrator scaling as configured — every leak in the course was a contract doing exactly what contracts do. The skill the course actually taught is holding both: trust the contract to work at speed, and know how to lift the lid when it doesn't.