Shouting Into The Void: A Raw API Rant for Anyone Who Gives A Damn

Warning: A Bit Ranty and Sweary

I like to think that I'm all about "keeping it real".

The reality is that I've just stepped down from my Zoom pulpit where I've presented a firehose of information on approaching API design to a data audience.

We reached 75 attendees at its peak. I believe I delivered a hyper-energised 45-minute presentation emphasising the significance of thinking about what you are building and why it matters.

This data congregation are a friendly bunch however I wonder if they were expecting more query parameters than value propositions.

A little more URL-based versioning over outcomes and alignment.

(les mots du jours)

One of my colleagues noted, "It felt like being hit by a freight train".

I took it to mean "energetic".

(Something that is in short supply at the end of November when everybody is focused on their annual creative writing exercise- the end-of-year review - *snark*)

Back to "keeping it real"

Last week there was a healthy discussion on LinkedIn started by Kin Lane on the topic of API Design First - dream or reality?

To echo the wisdom of Public Enemy: "Don't believe the hype"

A part of me wishes I had not read some of that thread a week before presenting on the topic of API design. It led me to ask: is what I am advocating even attainable? Is it more akin to chasing a mirage in the desert, always just out of reach?

Maybe lots of this stuff is not so common and we should all feel OK about that. For many of us, APIs are not the central focus of our product or our organisation for that matter. Existing APIs suffice for delivering business outcomes even if they make most of us scream FFS.

However, FFS is it any wonder?

I believe style guides are valuable for education and rationale but for FFS they are time-consuming. FFS they need to also be consumable, clear and actually create a decent API. I've been staring at it for months.

FFS creating and maintaining Spectral rulesets that are in line with your style guide, most likely in another Git repo. FFS don't forget the tests for the rule sets.

Sure we can trial API Design on one team at a time cos how else can we shave this yak?

FFS What even is an API strategy? Is anybody even using one? Do you honestly revisit it frequently?

FFS many are just getting heads around API Management and you go and unbundle them all.

FFS who can even afford to pay for all of these neat API tools? Many of us can't put our content on your servers so you are automatically ruled out.

FFS every conference feels like an overwhelming overview of all the things we are NOT doing.

FFS DOCUMENTATION STILL being massively under-invested but could yield the greatest benefits.

FFS if I never have to think about API versioning again.

FFS how is anybody meant to keep up with the blogs, conferences, LinkedIn, Mastodon, books, practices, trends?

FFS The API Landscape

FFS APIs - why do I still believe in your power to transform organisations?

Now can we all please start having some honest conversations in 2024?

Please feel free to add your own FFS rant below in the comments.