REST API Notes for 2018-07-26

Another week, another business trip. It not only has been a rainy July in Virginia, but there's been a steady drip-drip of API notes to check out. Let's dig in.



The first "Day Camp for Developers" virtual conference recently concluded. Ian Littman, who spoke at the event, has shared his deck "Load Testing your APIs". I love how Ian takes a pragmatic approach to his advice; rather than advocating to 'test all the things', he carefully lays out the different types of testing and when each is appropriate.


Watching from afar, the agile community is having something of a "dark night of the soul" moment. It is caused, in part, by the many misconceptions and half-truths that harried and ill-informed, yet well-meaning, individuals perpetuate in its name.

These folks are often the type that look at 'API-design-first' efforts and dismiss it as 'too waterfall'. James Higginbotham, who I work with on a regular basis, has a great piece on "API Design First in an Agile World". In it he revisits the agile manifesto, establishes a firm theoretical foundation, and then reconciles those core tenants with API-design first thinking. Highly recommended.


Kin Lane, the API Evangelist, recently posted a moving request for developers to use plan language in describing their APIs. I couldn't agree more. Just because I can order a meal in a restaurant or read a stop sign - the everyday, ordinary actions where the language processing centers of the brain are engaged - doesn't mean I am an effective communicator. To communicate well is a skill. Speaking in internal acronyms and localized jargon means inserting a comprehension barrier between you and the other parties. Putting ephemeral names - like teams or projects - into the paths is equally frustrating.

Involving a good product manager - someone who is skilled at evaluating user needs, and matching intent to their understanding - can help. Finding those product managers that can 'speak' API is challenging, but it can be done.



Last night I did a Mission Impossible themed sprint to update The goal was to move from the insecure http to https protocol for numerous reasons. The play-by-play is on Twitter). In the end, the design is bare-bones and Chrome hates the usage of Github cert with a custom domain name. #winning?

I'll have a full-write up, similar to what I did for my personal site, up shortly. In the meantime, if you have an upcoming, in-person Web API gathering that should be shared, let me know and I'll add it.

Also, if you'd like to show your support for this, and other, community efforts, check out my Patreon page.

Thank you for reading. Till next time, Matthew

@libel_vox and

Subscribe to Net API Notes

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.