The Business Value of a Good API
summary
Covers concrete costs (3.6 billion people affected and ~$1.7T lost from 2017 software failures) and argues APIs drive either technical debt vs software capital with longterm dollar impact. Shows an iterative, scenario-based process: write pseudocode/“phony” real code, automate tests, document architecture, and CI, and measure quality with readability, consistency, testability and stability. Offers actionable checklist (four C’s, review steps, questions to ask stakeholders) for designing or evaluating an API.
AI-written summary · about
chapters (7)
- 0:00Start
- 10:11creating an api is different than building an application
- 49:08writing your requirements
- 49:41review the requirements
- 53:07understand what are the most common usage scenarios
- 56:33begin by discussing your ideas with your customers
- 57:10provide realistic estimates of your upfront costs
related talks
01h 35mThe Business Value of a Good API
26mThe Business of APIs
23mGetting the numbers for API-driven transformation to add up
29mThe Business of APIs
25mAPI Business Value beyond Monetization
27mGetting the numbers for API-driven transformation to add up.
35mThe Good, The Bad and The API
28mImpact Intelligence for APIs