Nov 2, 2026 · 787 words · 4 min read

Foreword#

Christian Adell had publishers ready to sell this book. He gave it to you instead.

Let that sink in for a second. Christian has written four books with O’Reilly and Packt, including Network Programmability and Automation, the book so many of us learned this craft from. He had offers on the table for this one and turned them down, so every network engineer, architect and manager on the planet could read it for free, and anyone who wants to can translate it into their own language.

I self-published my first book, Automate Your Network, so I know what that choice costs: the late nights, the weekends, the editing passes that never seem to end. Christian did all of that, more than 150,000 words of it, while holding down a full-time job at a hyperscaler. He did it for fun, expecting nothing back, and that tells you who he is before you even reach page one.

If you’ve spent any time in the network automation community, you’ve already benefited from Christian’s work, whether you knew it or not. He was part of the team that proposed the NAF Framework, a community-built, vendor-agnostic reference architecture, and he has taken it to the AutoCon stage so the rest of us could put it to work. That framework is the backbone of this book.

Notice how he talks about it, though. He names every collaborator: Damien Garros, Claudia de Luna, Dinesh Dutt, Wim Henderickx, Srividya Iyer and Ryan Shaw. That’s Christian in a nutshell. The work is never about him; it’s about all of us getting better together.

What I love most about this book is that Christian shows you his scars. Almost every chapter opens with a failure story. There’s the logistics company whose shiny new Ansible platform buckled six weeks after an acquisition, and the cost optimizer that did exactly what it was told at three in the morning, then quietly wrecked performance once the daytime traffic arrived. Plenty of experts will tell you what worked. Very few will sit you down and walk you through how it broke, why it broke, and how to make sure it never happens to you. Those are the people worth learning from, and Christian is one of them.

(I’ll admit I also smiled when I spotted pyATS in Chapter 8, with the book Dan Wade and I wrote in the references. So yes, I’m a little biased. I’m also right.)

This book is a journey, and the order matters. It starts with why automation needs an architecture at all, then takes you through the building blocks one at a time: intent, the source of truth, execution, observability, orchestration, presentation, and the network itself.

From there it covers what most books skip. Running automation as a real platform, at scale, secure enough to answer an auditor’s questions. The human side, too: new roles, culture, and treating the network as a product. Only then does it climb to closed-loop automation, self-healing networks, and finally autonomous networks driven by AI agents.

That last chapter is my world these days, so let me say this as plainly as I can: the agentic future only works because of the seventeen chapters that come before it. An AI agent is only as good as the intent it’s given, the data it trusts, and the guardrails a human set for it. Christian gets that. He treats agents like a team working inside bounds that people define, not like magic.

If you’re excited about AI in networking (and you should be!), this book is how you build the foundation it can safely stand on. He’s even upfront that he used Claude as his editor. That kind of honesty is exactly what our industry needs more of right now.

One more chapter I have to call out: Chapter 14, Cultural Shift. Christian writes about the identity crisis that comes with automation, the moment you have to let go of the CLI expertise you spent years building. I lived that. Many of you are living it right now.

Read that chapter twice. It’s okay to be nervous about the leap, and there’s a whole community on the other side ready to catch you.

So here’s my ask. Read this book; it’s free, so there’s no excuse. Then do what Christian did and give something back. Report an error, translate a chapter, share your own horror story at the next AutoCon, or help the engineer sitting next to you write their first script, and then help them get past it.

Christian, thank you for writing the book so many of us needed, and for giving it away.

Now let’s go automate our networks.

John Capobianco
Head of AI & Developer Relations, Itential

📖 Enjoying the book? It is also available on Kindle and in paperback. Get it on Amazon →