Conceptual Clarity Marc Fournier Published May 17, 2026

The System Underneath

On This Piece
Most of us count every day without ever thinking about what counting actually is. This piece uses number systems - decimal, binary, hexadecimal, and the ancient Babylonian base sixty - to reveal something that applies far beyond mathematics: complex systems do not get simpler because we stop looking at them. The structure underneath is still there whether we understand it or not. A companion piece to Why Getting the Right Answer Isn't Enough, this lens builds the same case from a different angle - that surface familiarity is not the same as structural understanding, and confusing the two has consequences.
See Also
Why Getting the Right Answer Isnt Enough
Conceptual Clarity
Do you know how to count? It sounds like an odd question. Of course you do. You've been counting your whole life. But here's a strange one: what number is ten? If your answer is ten - you're right. But only in the system you're used to. In the decimal system - the one we all grew up with - the symbol ten means one group of ten, and zero ones. That's it. But in binary, the system computers run on, that same symbol - one, zero - means two. And in hexadecimal, the system programmers use, it means sixteen. Same symbol. Three different numbers. Because the symbol doesn't carry the meaning. The system does. In decimal, the base is ten. Each column represents a power of ten. In binary, the base is two. In hexadecimal, sixteen. The symbol stays the same. The structure underneath it changes everything. And decimal isn't even the oldest system. Four thousand years ago, the Babylonians counted in base sixty. Which is why we still have sixty seconds in a minute. Sixty minutes in an hour. Three hundred and sixty degrees in a circle. That's not a coincidence. That's a four-thousand-year-old number system quietly running underneath your daily life. So why don't programmers just read binary? Because inside a processor, billions of signals are switching on and off constantly - and binary strings get long very fast. So programmers group the digits and compress them into hexadecimal shorthand. It's a translation layer. A way of making the underlying system legible without having to look at all of it at once. Most of us never interact with any of this. And that's fine. You don't need to understand binary to use a computer. But the system is still there. It doesn't stop being complex because we stopped looking at it. That's the thing about complex systems. The surface can be completely familiar - and still be sitting on top of something most of us have never seen. Numbers are like that. So is language. So is infrastructure. So is almost everything we depend on but don't think about - because we don't have to. Because we have jobs, and lives, and a limited amount of hours in a day. Most of us aren't casually reading technical literature in our spare time. That's not a failure. That's just what bandwidth looks like. But it does mean that when complex things get reduced to something simple enough to fit in a conversation - a slogan, a headline, a bumper sticker - a lot gets left behind. Not because anyone's being dishonest. Just because that's the only form most of us have time for. The system underneath is still there. It was always there. And the people who understand it aren't making it complicated. It just is.