The Plumbers of Civilization

Ask a stranger to name a critical infrastructure sector and you'll get the greatest hits fast: the power grid, water systems, banking, maybe hospitals if they're feeling generous. Nobody says networking. It doesn't even make the cut as a supporting character. It's the roadie nobody claps for while the band takes its bow.

Networking engineers have made a strange kind of peace with that. We are the plumbers of civilization: unseen, unglamorous, and load-bearing. Nobody throws a parade for the person who kept the pipes from bursting. They throw a parade for whoever turned the tap and got water. The tap gets the credit. The pipe gets forgotten right up until it leaks.

The grid needs a grid of its own

Take the power grid, everyone's favorite example of Real Infrastructure. A grid operator doesn't run substations by sending someone out to eyeball a dial. Supervisory control systems, protection relays, phasor measurement units, the whole apparatus that lets an operator spot a fault three states away and shed load before it cascades, all of it rides on networks. Knock the network out and the power plants don't explode. The people meant to coordinate them simply go blind and deaf at the same moment. The grid's resilience story is quietly a networking resilience story wearing someone else's uniform.

Water systems run the same trick. Treatment plants and pump stations talk to their dosing controls over industrial networks that most customers assume don't exist, because why would anyone spend a Tuesday wondering how chlorine gets dosed correctly at three in the morning? They shouldn't have to, and that invisibility is exactly why the budget for it quietly evaporates: nobody protects a line item for a system they never knew was running.

Hospitals run on packets, not just on doctors

Healthcare makes the case even more bluntly. A modern hospital is a building full of devices that need to agree with each other: infusion pumps, imaging systems, patient monitors, the record system telling the night shift what the day shift already knew. None of that coordination happens by clipboard anymore, and when the network behind it has a bad afternoon, floors full of nurses go back to paper charts and hope nothing gets lost in the switch. The stethoscope isn't the hospital's most critical piece of technology. It's just the one people photograph.

Finance likes to imagine itself as a self-contained fortress of vaults and regulators, and it might be the most networking-dependent sector of the lot. Look past the vault imagery and a transaction is a message: formatted correctly, authenticated, routed through several intermediaries who all have to agree on what just happened, then settled somewhere well away from the screen you're staring at. Strip off the branding and a bank is a large, heavily regulated distributed system, and distributed systems are a networking problem before they're anything else.

None of this makes networking superior to the sectors sitting on top of it. It makes networking foundational in the plain structural sense: the layer nobody names because everything else gets built directly on top of it. You would only notice a foundation on the day it wasn't there, and by then noticing doesn't help much.

There's something almost comic about how reliably this gets left out of the public conversation, and I say that as someone who has made peace with roadie status. Policy debates treat grid hardening and hospital cybersecurity like two unrelated problems needing two unrelated fixes, when a meaningful share of the real risk sits one layer down, in the wires and routing decisions that let both keep talking to themselves. Harden the substation all you like. If the link reporting its status goes dark, congratulations, you've hardened a building whose alarm nobody can hear.

So no, networking doesn't get top billing, and it probably never will. Fine by us. We didn't get into this line of work for the applause. We got into it to make sure the applause has electricity to run the microphone.