Hi everyone 👋
I want to share a standalone piece I just published. It is a short detour from my Networking Foundations series, but it comes from the same instinct, so it felt worth writing.
Here is the idea.
As an infrastructure engineer, you learn not to start with the application a user sees. You start at the bottom of the stack and work up, because that is where the real constraints live. A website is only as available as the server beneath it. A server is only as reachable as the network beneath that. Control, capability, and failure all originate in the lower layers and cascade upward.
I took that exact instinct and pointed it at artificial intelligence. And through an infrastructure lens rather than a software one, something becomes clear that the louder conversations tend to miss.
AI is not really a software story. It is an infrastructure story.
Underneath every weightless little AI prompt sits a very physical stack: chips, data centres, electricity, cooling, water, land, and grid capacity. And each of those layers has a chokepoint, a place where a small number of actors control something everyone else depends on.
Consider just the energy layer. The single biggest constraint in the AI buildout right now is not chips or capital. It is electricity. In the largest data-centre hub on earth, some new projects have been warned they could wait up to seven years for a full grid connection. A single AI server rack can draw as much continuous power as a small building. The binding limit on AI is becoming physical.
Here is why that matters beyond the engineering. Because the layers are stacked, control of a lower layer cascades upward. Restrict who can buy advanced chips, and you have indirectly decided who can build data centres, which decides who can train models, which decides who can ship applications. You do not need to regulate a thousand applications if you control the one resource they all depend on.
The post also looks at the long history of critical infrastructure, railroads, steel, nuclear, the internet itself, and the consistent pattern of what happens once a technology becomes essential enough that a society cannot function without it.
I kept it deliberately structural rather than political. The point is not who is right or wrong. It is that infrastructure shapes what is possible, and that is an engineering truth, not a partisan one.
It also connects back to something personal. I once wrote about hitting paid usage limits on an AI tool and asking whether the pricing was exploiting how dependent I had become. This post is the structural answer to that frustration: the wall I kept hitting was placed several layers down the stack, in a room I would never see.
📖 Read it here: https://vickkykruzprogramming.dev/blog/the-infrastructure-lens-why-control-of-ai-lives-in-the-layers-underneath
It comes with four original diagrams, including the full five-layer AI infrastructure stack. Subscribe to my newsletter for more analysis that looks underneath the headlines.
Top comments (0)