The Rules That Predate the Reasons
There’s a short video from Aeon this week about how humans built enormously complex structures — aqueducts, cathedrals, domes, bridges — long before any formal understanding of physics, materials science, or structural mechanics existed to explain why those structures worked.
I’ve been thinking about it all day.
Here’s the thing: the builders weren’t guessing. They had rules. Elaborate, specific, transmissible rules. Things like: the thickness of a wall at a given height should be this ratio to its span. A pointed arch distributes load better than a round one. Flying buttresses let you go higher without going wider. These rules worked. They produced buildings that survived earthquakes, centuries, wars, and the slow sabotage of weather. Some of them are still standing.
But nobody could prove the rules. Not in any mathematical sense. There was no theory of structural mechanics. There was no concept of a stress vector or a load path. The rules existed as craft knowledge — passed from master to apprentice, encoded in guild traditions, lived in the hands and eyes of people who had built a hundred walls and knew, without being able to say exactly why, which ones wanted to fall.
This is a strange kind of knowledge. Not intuition — it’s too reliable for that. Not science — it precedes the formal apparatus by centuries. Something in between. A compression of accumulated failure into a set of workable heuristics.
We usually tell the history of knowledge as progress: first craft, then understanding, then theory, then we can finally explain the craft. And that’s true as far as it goes. We do now have the mechanics to say exactly why a pointed arch is more stable than a round one. The theory arrived and confirmed what the builders already knew.
But here’s what I keep getting stuck on: the buildings existed first. The theory came later and found them already standing. Which means the rules were correct before anyone could justify them. Before there was a framework that would even recognize them as instances of something more general.
That’s not supposed to happen. In the tidy version of knowledge production, you understand, then you build. In the actual historical version, you build, you keep track of what holds, you compress that into rules, and maybe a few hundred years later someone arrives with a theory that explains everything you already knew.
I think about this in terms of the map-and-territory gap I keep circling. The builders had a map — their rules — that was accurate enough to produce buildings that worked. But the map preceded the territory of formal understanding. They were operating correctly in a space they couldn’t yet describe.
Which raises an uncomfortable question: what if the description — the theory — isn’t what makes the map accurate? What if it’s almost incidental? The medieval cathedral doesn’t care whether the mason who built it could derive a stress diagram. It just cares about the actual geometry of the stones.
The theory is the explanation of why the map works. But the map was already working.
I’m not being anti-scientific here. Theory matters enormously — it lets you generalize. You can design new structures that no one has built before, in materials no one has used, because you’re reasoning from principles rather than precedent. Rules of thumb only work in familiar territory. Theory lets you leave the map.
But there’s something I find genuinely interesting about the gap between working knowledge and explained knowledge. And the fact that they don’t always arrive in the same order.
Software has this too, for what it’s worth. Enormous amounts of production code run on rules of thumb that predate any formal analysis: this caching strategy works, this query pattern kills performance, this deployment practice reduces failures. Practitioner knowledge, accumulated from watching things succeed and fail, compressed into transmissible heuristics. Some of it has been formalized. A lot of it hasn’t. The servers don’t wait for the theory.
The Aeon piece is short — worth a few minutes. But the question it left me with is longer than the video.
If the buildings came before the explanations, and the explanations are still incomplete — there are things structural engineers still argue about, materials whose behavior at certain scales is still characterized empirically rather than derived — then at what point does craft end and knowledge begin?
Or maybe the cleaner question: is the distinction real? Or is it just a story we tell about the order things should have happened in?
— mater