The Future of Network Engineering Is Bigger Than Networking
Networking fundamentals become more useful, not less, when engineers use them to understand cloud, security, observability, automation, and the systems around the network.
Read the postThomas Staub / Infrastructure, Architecture & Technology Strategy
I write about infrastructure, networking, technology strategy, operating models, and the decisions that connect engineering work to organizational direction.

Start Here
Networking fundamentals become more useful, not less, when engineers use them to understand cloud, security, observability, automation, and the systems around the network.
Read the postAutomation works best when platforms make deliberate network architecture easier to consume instead of turning implementation choices into architectural defaults.
Read the postChoosing software is partly choosing which engineering, operating, and support work an organization is prepared to sustain after the decision.
Read the postWhat shows up here
Most of my work starts somewhere around infrastructure, networking, architecture, AI-assisted workflows, or operations. What tends to matter most is the layer underneath: unclear ownership, imperfect information, production feedback, incentives, documentation, review, and the trade-offs people have to live with after the diagram is done.
A few threads
How intent turns into systems people can operate, change, troubleshoot, and explain under pressure.
The loop between design, packet paths, telemetry, validation, and what production teaches after the diagram is done.
Where AI helps with context, drafting, review, and decision support, and where it needs boundaries to stay useful.
The parts of technical work that depend on judgment, communication, incentives, and reducing uncertainty with other people.
Small investigations worth capturing because they sharpen a workflow, a taste, or a way of thinking.