In this episode of the Network Automation Journey I talk about some other criticisms of network automation that I've heard of lately. 

One of primary the factors pushing organizations into embracing network automation is the need to dynamically generate complex configurations, specifically for campus and data center implementations of EVPN/VXLAN. 

Different devices have different native configuration methods. Generally they're either syntax (think Cisco IOS) or state-based (more rare, like Cisco ACI). 

When I teach an automation course, I'll typically show a video: https://www.youtube.com/watch?v=HluANRwPyNo (a bit of foul language in it... but very realistic use of it)

In networking, everyone Google's everything. Got an error message? Google Search. Can't remember how to do something? Google Search. The same is true in network automation. 

Also, this comic from XKCD: https://xkcd.com/979/

Recent discussions on Twitter and in a few classes brought up the venerable VI editor (or the more common upgrade to VI, VIM). 

It was once a must-learn tool for Unix/Linux/BSD administrators. It was used for editing configuration files, data entry, and even coding. 

These days it's not quite the must-have it used to be. In fact, most people working in the industry can get by with the less capable, but far easier to learn, nano editor. 

In this episode, I talk about stunted careers, people (including myself at one point) that just won't learn anything new, despite the world passing them by. Luckily I got out of my stunted phase relatively quickly, but it's something I see in networking from time to time. 

Bad Takes: Is Ansible just automation for people who don't know Python? Of course not. And we'll talk about why.

@el_dude_abides asked a few more excellent questions which I did my best to answer:

One of the most important skills in network automation is to know your way around YAML files and JSON, to know the difference between lists and dictionaries, and how to iterate through them. 

In this episode, I talk briefly about two different depths of automation: Supplemental and Total. 

With supplemental automation, automation is used only on part of a config (SSH keys, DNS, NTP, etc.) while the rest of the device is configured in the traditional (i.e. manual) way. 

With complete automation, no more manual configuration is done and the entire configuration is done through some sort of automated means.