Posted on 07-17-2014
In the API space it is easy to recognize the cool kids, the ones that are in the know. These types of personalities just understand how to get things done, don't take no for an answer, and understand the DIY, self-service nature of APIs.
I get a lot of folks who ask me to add them to my API Management provider section, or my API Integration area. I always add these people to my Evernote queue, and when I get time I go through and profile them, I add them to my master CRM, and when I publish the latest round of content and data to the API Evangelist network site in question, the blog post, or company listing will be updated—something that can take minutes or weeks, depending on my workload.
In contrast, the savvy people in the space, understand that the API Evangelist network runs on Github, as 60+ separate research projects, and that they can add themselves. All you do is fork the project you want to update, add yourself to the blog post, or the JSON file that drives the data listing, and submit a pull request. I don’t always guarantee I will accept your addition, but if it is correct, and brings value to the API community, there is a good chance I will.
I just finished publishing a list of all of the SendGrid developer evangelists, and I mistakenly left off Will Smidlein (@ws), one of the SendGrid developer evangelists. Will, being one of the cool kids, didn’t ask, he just forked API Evangelist, added himself to the list, and submitted a pull request. Minutes later, he’s on the blog, listed correctly as one of the evangelist.
I wonder how long it will take for more of my audience to realize they can help curate, and publish to API Evangelist, right alongside me--it has been this way since January of 2013. ;-)
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- I Am Using Kimono Labs To Fill In Gap For Companies Who Do Not Have AN RSS Feed For Their Blog
- Someone Please Build My Open, Interactive, Portable, And Visual API Documentation Toolkit
- Dwolla Using Slate For An Evolved API Documentation Experience
- Crazy Mess Of URLs Across 400 Of The APIs In My Stack
- Reworking My API 101 Content: Consuming APIs
- I Need Help To Make Sure The Dept. of Agriculture Leads With APIs In Their Parks and Recreation RFP
- What Is The Biggest Challenge For Fraud Detection API SiftScience?
- Reworking My API 101 Content: Providing APIs
- What I Spent Ada Lovelace Day Working On
- An Outside-In Approach To Jumpstarting An API Effort At The University of Oklahoma