API-jinks

Network programmability is a very hot topic. Developers are looking to the future when REST APIs and Python replaces the traditional command line interface (CLI). The ability to write programs to interface with the network and build on functionality is spurring people to integrate networking with DevOps. But what happens if the foundation of the programmable network, the API, isn’t the rock we all hope it will be?
Shiny API People
APIs enable the world we live in today. Whether you’re writing for POSIX or JSON or even the Microsoft Windows API, you’re interacting with software to accomplish a goal. The ability to use these standard interfaces makes software predictable and repeatable. Think of an API as interchangeable parts for software. By giving developers a way to extract information or interact the same way every time, we can write applications that just work.
APIs are hard work though. Writing and documenting those functions takes time and effort. The API guidelines from Microsoft and Apple can be hundreds or even thousands of pages long depending on which parts you are looking at. They can cover exciting features like media services or mundane options like buttons and toolbars. But each of these Continue reading
CC BY 2.0 by 


CC BY 2.0 by 
