Cisco Chat: Have APIs killed the CLI?
Have you heard of Cisco DEVNET?
We are the single resource for everything ‘developer’ at Cisco, and we are here to help you learn, code, inspire and connect.
One of our favorite partnerships is with the Systems Engineering organization, #CiscoSE. Together, we are hosting a #CiscoChat to answer this question: “Have APIs killed the CLI?”
What’a an API? What’s a CLI? What’s a developer?
Bring all your questions to Twitter on March 22.
Prior to the chat, make sure to claim your #DEVNET account!
Let us know you registered by sending us a tweet @CiscoDevNet
Is this a Systems Engineer or a Developer?
Actually, Hank is both.
“If you want my CLI, you’ll have to pry it from my cold dead hands!”
Maybe an extreme example, but that seems to be the fear of many network engineers.
But is the CLI really at risk of going away? Or, can new network APIs and the CLI happily co-exist?
In this #CiscoChat, “Have APIs Killed the CLI” we’ll consider this question, and have an honest discussion about the future of the beloved CLI, what new APIs offer the network engineer, and how to pick the right tool for the job.
What’s it like working at DEVNET?
I love being the developer’s advocate and sharing code “things” I think are cool, DEVNET allows me to do that and so much more! Here’s an example.
John McDonough, DevNet Evangelist