Automation and “network as code” have become more than just buzzwords, they’re the life blood of modern enterprise networking. Pete Welcher is onboard for this, and is enthusiastic about how automation and code can help increase efficiency and make life a little easier.
But in the rush to praise these two, there’s often a dearth of critical conversation around drawbacks and limitations. That’s what makes Pete’s recent piece so interesting. This isn’t someone being a curmudgeon, complaining about something new. Instead it’s an advocate who is nonetheless critical of the often unspoken issues in network automation.
The big issue that struck me was the dearth of quality API documentation. I’ll admit to have not really worked with APIs in any meaningful way. I guess I assumed they had the equivalent of man pages, with fully explicit lists of modifiers, outputs, etc. Instead, in Pete’s experience, it’s very hit or miss, depending on the approach of the author.
Pete Welcher comments:
I have yet to encounter what I’d call good API documentation, i.e. that doesn’t require reading the mind of the person who wrote it. Maybe that says something about me, or the vendor API’s I’ve been exploring.
- Gestalt News for the Week of October 14, 2019 - October 14, 2019
- The Rise of Semi-Custom Silicon - October 11, 2019
- VMware Takes the Carbon Black | Gestalt IT Rundown: October 9, 2019 - October 9, 2019
- Learning Kubernetes is a Waste of Time – The On-Premise IT Roundtable - October 8, 2019
- Gestalt News for the Week of October 7, 2019 - October 7, 2019
- What Happened to Docker? - October 4, 2019
- WeWork’s IP-No | Gestalt IT Rundown: October 2, 2019 - October 2, 2019
- Gestalt News for the Week of September 30, 2019 - September 30, 2019
- Is Slack Doomed? - September 27, 2019
- Not Hot For Bots | Gestalt IT Rundown: September 25, 2019 - September 25, 2019