The Business Value of a Good API

By Bob Steagall

As programmers, we use APIs every day, whether it is at the library level, the subsystem level, or the individual component level. And yet, using many existing APIs is often an unsatisfying experience, for any number of reasons: poor documentation, confusing component interfaces, muddled abstractions, broken/missing functionality, etc.

So how can we distinguish between a good API and a bad API? More importantly, how can we make the argument to our managers that good APIs, whether obtained off-the-shelf or built in-house, are a prudent investment?

This talk seeks to discuss these questions and perhaps provide some answers. We’ll look at specific criteria for evaluating the goodness and/or badness of an API. We’ll cover the concepts of technical debt and software capital, and define a relationship between them and API goodness/badness. We’ll also discuss a simple iterative process for building APIs which can help avoid technical debt and increase software capital. Finally, we’ll cover some recommendations for doing evaluations, using the process in day-to-day work, and convincing management of your wisdom.

Your Privacy

By clicking "Accept Non-Essential Cookies" you agree ACCU can store non-essential cookies on your device and disclose information in accordance with our Privacy Policy and Cookie Policy.

Current Setting: Non-Essential Cookies REJECTED

By clicking "Include Third Party Content" you agree ACCU can forward your IP address to third-party sites (such as YouTube) to enhance the information presented on this site, and that third-party sites may store cookies on your device.

Current Setting: Third Party Content EXCLUDED

Settings can be changed at any time from the Cookie Policy page.