The Network Automation Paradox - You Need Time To Save Time
Everyone says network engineers need to automate.
Learn Python. Learn Ansible. Build a source of truth. Learn Git. Test your changes. Stop doing everything manually.
There’s just one problem:
When?
At AutoCon 5 in Munich, Andy Lapteff sits down with Dutch network automation consultants Bart Dorlandt and Bart Smeding for a conversation that starts with Python and eventually lands somewhere much more interesting: time.
Automation can turn three hours of work into three minutes. But getting there requires engineers to invest time they often don’t have, or don’t feel permitted to protect.
Andy knows that firsthand. At one point in his career, his manager gave him an entire day every week to learn automation. Instead, Andy kept using that day to catch up on operational work.
Why?
That question opens a much bigger conversation about engineering culture, burnout, professional identity, European and American attitudes toward work, change freezes, technical debt, and the endless tension between keeping today’s network running and building a better way to operate it tomorrow.
This isn’t another lecture telling network engineers to “learn Python.”
It’s a conversation about why that advice is so much easier to give than to follow, and what has to change if we want network automation to become common.
Bart Dorlandt:
https://www.linkedin.com/in/bartdorlandt/
Bart Smeding:
https://www.linkedin.com/in/bartsmeding/
For everything AONE: https://artofnetworkengineering.com/