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 / vStaub
Some posts will be technical. Some will be about decisions, trade-offs, career, operating models, and the human systems around engineering. Mostly, this is a place to document what I'm learning.

Latest Posts
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 postGood network automation asks consumers for the outcome they need, then derives the implementation details the network already knows how to provide.
Read the postDurable segmentation starts by defining required communication and its consequences before choosing how to enforce it.
Read the postWhat shows up here
Most of my work starts somewhere around infrastructure, networking, architecture, AI-assisted workflows, or operations. But the interesting part is usually 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.