Network Automation with David

You’re Asked to Automate the Network. Now What?

In the very beginning… Whether you are an administrator, an engineer, or an architect, the moment you are asked to automate the network, you are stepping into a new world. A world full of possibilities, but also challenges. The first question that often comes up is simple: where do I even start? For an administrator dealing with tickets and day-to-day changes, the idea of automation can feel overwhelming. For an engineer, it might immediately become a question of tools and languages. For an architect, it’s about designing a system that can scale, adapt, and remain maintainable over time.

Why I Chose Network Automation (and Why I’m Writing About It)

A short introduction I started my career in IT in 2008 on a service desk. Back then, networking felt very tangible. You logged in, made a change, verified it, moved on to the next ticket. It was manual, repetitive, and for a long time, that was simply how things were done. Over the years, the scale changed. Networks grew larger, more complex, and more critical. The number of changes increased, but the time and attention available did not. That was the moment when doing things “the old way” stopped being sustainable.

My first blog post

My first blog post! Everything seems to be working alright, so many topics to post about. More to come soon ⚡