As an #API enthusiast, I've been promoting API usage for over 10 years. However, despite the growing adoption of #APIs among developers, I've noticed a worrying lack of awareness about the risks of relying on (external) APIs. Here's a thread: 👇

You can now find me on Bluesky:

"By maintaining an up-to-date #API landscape, organizations can ensure smoother workflows, effective bug fixing, and resource optimization, ultimately contributing to improved efficiency and collaboration within the organization." https://t.co/g9CbgmyFnB

I've just published my first blogpost on Medium! Please let me know what you think ;-) "Dealing with the #API Lifecycle’s End-of-Life Phase: Best Practices for API Consumers" https://t.co/429HPu1ySN

I still find it confusing that the info.version field of the @OpenApiSpec is the only info field not about the API but about the document itself, as the info object "provides metadata about the API", according to https://t.co/12RL1NuTBl.

Happy to present a session at @AppdevconNL again! https://t.co/6er8X4p2vF #apis #apidependencymanagement

Last week, our Senate enacted a law so they can oblige government orgs in the Netherlands to use digital standards enlisted in our standardization agency. Proud of my contribution to get @OpenApiSpec on that list, which means that every gov #API should come with an #openapi spec!

Interested in @OpenApiSpec, @jsonschema and https://t.co/vra0mVAj6N? Looking for a #gsoc #gsoc2023 project to work on? Have a look at this Github repository, and check out the 'good first issues'. RTs appreciated. #APIs #OpenAPI #JSONschema

OpenAI is hiring a Killswitch Engineer for GPT-5. Apply now.

My mission is to raise awareness about this issue and encourage developers to take a more active role in managing their API dependencies. In the coming weeks, I'll be publishing a series of blog posts on this topic, so stay tuned! #APIs #API #developers

By doing so, we can minimize the risks involved in using APIs and be better prepared for when something goes wrong. We can also be more proactive in seeking alternatives or developing fallback strategies.

That's why I believe that API consumers should take more responsibility for the APIs they use. Just like we write tests, document our code, and maintain deployment flows, we should also keep track of the APIs we use and how they fit into our applications.

For example, if an API you're using goes down, is deprecated, or its new owner suddenly decides to change the policy (you know what I mean 😉), your system may break or behave unpredictably. If you don't have a plan in place to handle such situations, you may be in trouble.

When you use an API, you're introducing a new dependency into your application. You need to know which version of the API you're using, what its purpose is, and how to use it correctly. Otherwise, you may be exposing your app to unnecessary risks.

APIs are everywhere in the IT industry (and that's a good thing!), and they can bring a lot of benefits, but also risks. As both an API consumer and provider, I've noticed that many developers and digital agencies are not aware of the risks involved in relying on APIs.

🚀 Introducing the new Apiwatch! Keep track of your #API landscape in one central location. Don't let changes, disruptions, or deprecations catch you off guard. Sign up for a free account now at https://t.co/sz0oPIkPQK #apimanagement #apistrategy #apilandscape

Still not sure about this, so let's ask the community. How do you call an organization publishing/providing an #API? Which role do I have running an API-as-a-Product?

New @Gartner_IT API Survey dropped! - 98% of orgs use/plan to use internal APIs (88% in 2019) - 94% of orgs use/plan to use public APIs (52% in 2019) - 90% of orgs use/plan to use partner APIs (68% in 2019) - 80% of orgs provide/plan to provide publicly exposed APIs (46% in 2019)

NASA-wetenschappers ontdekken nooit eerder vertoonde bureaubladachtergrond van Windows 98

🚀 Check out @saasmanagerio’s brand new website they recently completely build and launched with Framer! https://t.co/B7h6W6X2k8