One API ecosystem challenge I've had over the years is quantifying what "good" looks like (I've published that journey on my website, with pieces including "Rethinking NPS for Quality" and "How Reporting Can Backfire" ). Despite most organizations' desire to be "data-driven", much of the quality storytelling we do remains anecdotal and story driven.
On the one hand, quantifying abstract concepts like "maturity", "quality", or "maintainability" is problematic. On the other hand, quantifiable metrics like "time-to-hello-world" and "uptime percentile" don't describe the health of an API ecosystem or whether improvement efforts are improving the speed and safety of overall API development.
I joined Postman in April, just as the company was preparing its latest survey. I saw it as an opportunity to build upon existing industry devops insights by testing whether they also apply to API program performance.
In the 180th Net #API Notes, I deep dive on the Postman 2021 State of the APIs Report; specifically, what are the four behaviors of high-performing API teams? And how do we measure them?
More in the newsletter:
https://tinyletter.com/NetAPINotes/letters/net-api-notes-for-2021-11-04-issue-180-state-of-the-api-report
Top comments (0)