Nutrients for Writing

I spent two days at API Days in NYC last week talking APIs, and in the lead up to the conference I didn’t do much writing, focusing my energy on my keynote and being present. Coming out of the conference I haven’t done any writing because I don’t have any mojo. It is now a week since the last day of the conference and I am only just now writing anything in my notebook and hitting publish on API Evangelist and Kin Lane. The experience took it out of me.

In the old days I used to find a lot of inspiration at these events. Today, it was all about AI and MCP, and resisting or responding to AI and MCP. While there were small pockets of interesting conversations and worthy technological innovation, the majority of engagements centered on AI and MCP. It is something left me extremely deficient in the nutrients I need for writing on APIs, in a time where I am already struggling significantly to care and put words down on “paper”.

I depend on feedback loops with the community to write on API Evangelist. Those feedback loops are almost non-existent. The conversations felt like they were generated in ChatGPT. There were a handful of kindred souls in the mix that I will exclude from this, but the majority felt like a predictive output of what you should be discussing at a technology conference. I need to figure out where I can find more nutrients to keep me publishing on API Evangelist—to find it I may have to just work from legacy notes, and the international conversations I am having with companies staying focused on the fundamentals of technology in their world.