I have to manually roll the blog for my website over each year. The primary link for my blog goes to whatever the most recent year is, which is a static page. I like it this way. It forces me to manually turn the page each year, which provides the opportunity for a (hopefully) thoughtful post about what is happening. I’ve never been one to look forward and do predictions for the coming year, but have been known to reflect back on the year that just happened. I don’t feel compelled to do either this year, but I still need a post to turn the page.
API Evangelist continues to live on after fifteen years of publishing. It is still my notebook for making sense of the technology, business, and politics of APIs. It is where I still work to work develop the policies that will matter to people, and shine a light on what is needed to govern the pipes we use in desktop, web, mobile, device, network, and now AI applications. It is where I still express regularly that there is bias in the system we depend on to run our world, using my algorotoscope work. After multiple burnouts where I stopped caring, I still very deeply care about writing and telling stories on API Evangelist. It is my muse. It is my voice. It is my sanity in an increasingly dystopian and uncaring digital landscape.
I am so very thankful for the last fifteen years of this website. I have no regrets. API Evangelist has given me purpose and allowed me to make a living. Even though APIs are noticeably falling out of fashion with investors, and under relentless assaults from every new wave of technological acronyms, APIs remain extremely important to everything we do. I have managed to find a productivity perspective on the artificial intelligence craziness using API Evangelist. I find that there is some sanity staying at the API line, stopping short of the rabbit hole of each application realm, and just being the expert who understands interfaces and the integrations between our applications and systems.
This year, I have also established Naftiko, with Jerome Louvel. My role as Chief Community officer very much reflects the API line in 2025. Open-source API standards and tooling make up this frontline today. It is how this frontline is being negotiated, hustled, and shapeshifted in 2025. MCP and A2A are coming for your API, despite being APIs. There is a lot of room for storytelling at this line, but it takes work to understand what truly matters—-this is the work I get to do as API Evangelist, but also while building Naftiko. The Naftiko Framework, Engine, and Fabric reflect this moment and the API frontline for any type of applications, and I am excited to get to work with Jerome and team to build it.
There is a lot of uncertainty in the world right now. I don’t feel like celebrating anything tech right now. I don’t feel any need to celebrate anything API related in 2026 with everything going on in the world. I do feel resolute that it is important for me to pay attention to the API pipes, shine a light on existing open-source tooling and services, while also working to contribute some commercial open-source solutions into the mix to try and build a successful viable company. Honestly, I don’t think we need more APIs–we have plenty. I am not a believer in AI, but determined to understand how it is being used. So moving into 2026 I cautiously celebrate 15 years as the API Evangelist, and I am optimistic for what I am building at Naftiko, but do not feel like it is a moment in time for moving posts about what is happening in the world of technology, with everyone it is enabling in the world–leaving us in a precarious position.
