The Trinity

Meet the Trinity

Three things, working together. Everything else in this course — every line of C, every algorithm, every AI model — is built on top of these three.

The chef can't cook directly from the pantry. Too many trips, too slow. So the chef brings ingredients to the counter first, works from there, and only goes back to the pantry when needed. That's it. That one detail — fast-but-small next to the worker, slow-but-huge in the back — is the root of basically everything interesting software does.

Why speed becomes everything

Look at how long each layer takes to reach. The numbers below are rough — machines vary, but the relative gaps stay pretty consistent across all of computing history.

(Bars are clamped at the RAM scale — past that, drawing them to scale would burst the page.)

Every performance problem you'll ever debug comes back to this chart. Big-O analysis, cache optimization, database indexes, "why is this slow?" — all of it is downstream from those latency gaps.

A program is just a recipe

What actually happens, second by second, when you tap the Safari icon? The whole sequence is a kitchen running an order:

1. Order arrives. You tap the Safari icon. The OS — the kitchen's maître d' — tells the chef there's a new ticket.
2. Recipe pulled from the pantry. The OS reads Safari.app from the SSD into RAM. This is the slow part of any program launch — pantry latency.
3. Mise en place. The recipe and the data it needs go on the counter (RAM). The bits being touched right now get pulled even closer — into the chef's hands (L1/L2 cache).
4. Cook. The chef executes one instruction at a time. Decode, execute, write the result back. Decode, execute, write. Billions of times a second.
5. Plate. The result hits the screen. (How that actually works lives in Week 8 — the GPU.)
6. Cleanup. When you quit Safari, the counter is wiped. The pantry still has the recipe for next time.

Every program ever written — whether it's a Python notebook, a Chrome tab, an AI model crunching inference, a video game, a web server — is running in this same kitchen. The programs get more complex. The kitchen stays basically the same.

What happens when the counter is full

Open Chrome. Open thirty tabs. Watch your machine slow to a crawl.

Your counter is overflowing. When RAM fills up, the OS spills the least-recently-used stuff back to storage — into a region of the SSD called swap. Next time the chef needs it, that's a 100,000 ns trip instead of 100 ns. Your machine isn't "tired" or "slow" — it's just making constant runs to the pantry.

This is why adding more RAM feels like a miracle fix. You're not making the chef faster. You're making the counter bigger so the chef stops making pantry runs.

What's next

You now have the kitchen. Next week we walk one floor deeper, into the chef's brain — and discover that "reading an instruction" is, secretly, just flipping switches with light.

Week 02 is The Language of Light — electricity, transistors, and binary. Why the entire 80-year history of computing rests on a single, almost embarrassingly simple idea.