Companion to COMPUTER_SYSTEMS_MASTERY_CURRICULUM.md Written April 30, 2026 — honest reflections, no sugar coating.
Opening Reflection #
You have probably been programming professionally for years without understanding how a computer actually works. That is not an insult — it is a testament to how good the abstractions are. You type rails server, a web application starts, and somewhere between your keyboard and the browser, electrons are doing something. This module is about finding out what that something is.
Charles Petzold's Code: The Hidden Language of Computer Hardware and Software is one of the greatest nonfiction books ever written. I say that without qualification. It takes you from flashlights and Morse code to a working computer, and it assumes you know nothing. It is patient, brilliant, and occasionally funny. Most technical books age poorly. Code, published in 1999, has not aged a day because physics has not changed.
The danger with this module is that you will skim it. You will think, "I already use computers productively, I know what a CPU does, I can skip ahead to the real stuff." Do not do this. Every module that follows — C, architecture, operating systems, networking — depends on the mental model you build here. If your foundation is shaky, everything above it wobbles.
What Will Surprise You #
Binary is not just "ones and zeros." It is a complete system of logic, arithmetic, and representation that maps directly to physical circuits. When Petzold shows you how a relay can compute, something will click that no amount of high-level programming prepares you for. You will realize that AND, OR, and NOT are not just Ruby operators — they are physical things you can build with wire.
You will also be surprised by how recent all of this is. The transistor was invented in 1947. The integrated circuit in 1958. The entire edifice of modern computing fits within one human lifetime. We are still at the beginning.
What Will Be Hard #
Patience. You are used to building things. You ship features, you write tests, you deploy. This module asks you to sit with ideas. To trace circuits on paper. To think in binary until it feels natural. There is no bundle exec moment. There is no green test suite. The reward is understanding, and understanding takes time.
Number systems (binary, hex, octal) will feel tedious until they do not. The transition happens suddenly — one day you look at 0xFF and just see 255. But the days before that transition are annoying.
What Will Be Easy #
You already think in layers of abstraction. Rails is nothing if not layers: HTTP to Rack to Router to Controller to Model to SQL to disk. That mental habit — "what is this layer hiding from me?" — is exactly the right question for this module. You will ask it instinctively.
Boolean logic will feel immediately familiar. You write conditionals every day. You already know that && short-circuits. You already know De Morgan's Laws even if you do not know the name. The formalization will feel like giving names to things you already do.
Computer Science Distilled will be a fast read for you. It covers algorithms and data structures at a high level, and you have already been using most of them through Ruby's standard library. It serves as a quick map of the territory before you go deep.
What I Am Watching For #
I will be watching for the "I already know this" trap. You do not already know this. You know how to use the results of this knowledge. That is different. A race car driver and a mechanical engineer both understand cars, but they understand different things.
I will also be watching for you to rush to Module 1 (C programming) before this module settles. The temptation will be strong — C feels like "real programming" and this feels like "theory." Resist. The theory here is what makes the practice in Module 1 make sense.
Predictions #
-
You will finish Code and immediately want to recommend it to someone. It is that kind of book.
-
You will struggle with the relay-based adder diagrams for about 20 minutes, then have a sudden moment of clarity that makes you say something out loud.
-
You will start noticing binary and hex everywhere — in Rails logs, in memory addresses, in color codes — and feel mildly annoyed that you never paid attention before.
-
Computer Science Distilled will take you two days. Code will take you two weeks. The two weeks will be worth more.
-
By the end of this module, you will understand why your MacBook has "16 GB of RAM" and what that number actually means physically. And it will bother you that it took this long to find out.
Closing Thought #
There is no shame in starting here. There is only shame in thinking you are above it. The best engineers I have seen are the ones who can move fluidly between "what does the user need?" and "what is the hardware doing?" You already have the first skill. This module gives you the second.