National resilience plans draw a tidy line at the border and assume critical systems stop there. Fiber and power grids never got that memo, and neither does money.
The unglamorous physical side of protecting critical infrastructure gets a fraction of the budget and respect firewalls do, and a confident stranger with a clipboard can end the whole argument in about ninety seconds.
Redundancy is easy to buy and easy to show off. Resilience is harder, messier, and the thing that saves you when nobody saw the failure coming.
N+1 sounds like a guarantee until you ask what N was and where the extra unit lives. A plain look at why the number means less than the sales deck implies.
Power grids, water systems, hospitals, and banks all get top billing as critical infrastructure. The networks that let their own control systems talk to each other get none of the credit and most of the blame when something goes dark.
The line between "critical infrastructure" and everything else is drawn by cascading dependency and political horse-trading in roughly equal parts, which is how a boring data center outranks your favorite bakery.
The concrete, unglamorous things I notice and do when I'm burned out, and why none of it is a system anyone else should copy. The closing post in a twelve-part series about mental health and this kind of work.
On the particular satisfaction of a technical win nobody else will ever know happened, and the quiet discipline of letting it count anyway.
Most of what goes into a solo project never becomes something you can hand someone else, and that turns evenings into a specific kind of quiet. A few rare conversations, with people who already know the terrain, cut straight through it.
On the specific discomfort of publishing an honest account of your own mistake under your own name, and the work of separating a flawed build from a flawed self.