Designing and writing good API documentation can be a daunting task, but is critical for any API-driven or B2D (Business 2 Developer) company to ensure developer success. Your documentation is also your company’s marketing asset and may be the first few pages a new prospect visits to assess how difficult your integration is and how the product works. Read more
In our post on ChatOps bot frameworks we discussed Hubot and how this widely forked project is a readily extensible mechanism for creating your own ChatOps bots. In this post we take a look at building such an extension in the form of a Hubot to help administer the Amazon API Gateway. Read more
Since GitHub integrated ChatOps into their operational strata, the concept has garnered a good deal of excitement. Essentially, ChatOps moves system operations into a group chat room, enabling developers to collaborate, initiate tests, deploy software, and build a company culture all from a single unified command line. Read more
What is a consistent attribute across successful API programs? They all have awesome developer portals. Good API documentation is easy to navigate and understand, but the best, shining developer center pushes onboarding and actual implementation to new levels of usability, to the point where integrating the API becomes as simple as cake — well, at least as simple as technically possible. Read more
Understanding the difference between an API (Application Programming Interface) and an SDK (Software Development Kit), and knowing when to provide each, is incredibly important for fostering a developer ecosystem. In the modern development landscape, these two tools and the synchronicity between them are the driving force behind web communication and the implementation of third-party APIs. Read more
