“APIs are as much about hiding complexity as they are about exposing capability.” —Mehdi Medjaoui

“The public doesn’t understand their city’s complexity and they don’t care about it. Similarly, users don’t care about your system’s complexity. They’re not internal to your organization. It’s not their job.” —@civicunrest

@civicunrest on APIs transforming govt:

• City govts all do similar things, but tools/practices vary greatly for no good reason. They reinvent because there hasn’t been a better way.
• Most govt APIs so far focused on exposing data, not capabilities
• Legislation, internal needs and policies, and product innovation (competing with private sector) are changing this!
• Early progress in cooperatively built/maintained software, investment in open source components, and data standards

Quotes from Erik Wilde’s talk at

“Nobody wants APIs. They want to get stuff done. Everyone needs APIs, but APIs are not the important thing. The important thing is the capability we wrap in the API.”

“If you wrap something super duper useful in a badly designed API, people will still use it! They won’t be happy, but they’ll still use it.”

Erik reached same conclusion I did about developer experience. is important, but does not matter as much as API providers want to believe.

If you have a productive, hacking cough do 👏 not 👏 attend 👏 a conference in-person. You are a biohazard. JFC… Did the pandemic not teach y’all anything‽

Scaling is the new API challenge for banking-as-a-service.

“‘Embedded finance’ will lead to more hypermedia style APIs.” —John Phenix, Lead API, Integration and BaaS Architect at HSBC

Embedding a bank’s UI into a partner app does not feel seamlessly integrated.

Getting partner to write complex UIs negates the ease of working with a banking partner.

A partner rendering its own UI based on the bank’s logic is the winning solution for best end UX and low integration effort.

The data and API governance practices described at L'Oréal seem more mature than anything I saw at Spotify and Stripe. I took a photo of nearly every slide they presented. So much great stuff.

For the 10 year anniversary of , the conference organizers asked speakers to do a 2022 update to their first talk given at the conference.

Ori Pekelman updated his talk on the problems of REST-ifying SOAP APIs to be the problems of GraphQL-ifying REST APIs.

The update: Actually GraphQL does not give you benefits over REST for most use cases and you cannot escape intentional domain modeling just because you have strong types built into the API style. 👏

First hour at an in-person conference and I have decided i am not yet comfortable attending in-person conferences again just yet.


Top API-related challenges in business:

1. Lack of API-specific product manager
2. Lack of predefined standard
3. Lack of API-related engineering skills

Biggest market opportunity: API management for *consumption* of APIs. The focus of API management so far has been almost exclusively for API producers.

—Mark O’Neill, VP Research at Gartner

🤯 @mamund has connected humanity, technology, history, and the future masterfully in every talk I have ever heard him give.

“Those who ignore the mistakes of the future are bound to make them.” —Joseph Miller, 2006

It’s been way too long since I have gotten to see Mehdi Medjaoui on a stage and asking questions.

(Feel free to mute me or this hashtag for the next 2 days.)

My SAS flight is winter weather delayed and I will miss this afternoon’s sessions, but I am en route to !

Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml