The current API development space is very self-ruled, in that web API developers have freed themselves of earlier SOA attempts to rigidly define and ultimately constricted API growth, into a more grassroots, community-owned approach to RESTful API design.
You can see this happen in real-time on the public Google Group called API Craft. API Craft was started by Apigee, as an open forum for sharing and developing knowledge and skills around APIs, where you can find the latest throughts, from the smartest people in the space.
I thoroughly enjoy the online version of API Craft, and just experienced my first offline version of API Craft at OSCON in Portland this week. Several API folks got together for beers and API Craft discussion at the White Eagle Saloon creating an awesome real-time, face-to-face extension of the online API Craft group--an experience I intend to initiate whenever I am in new cities around the country, and I encourage you to do the same.
I think Apigee has really started something important and feeling inspired, I wanted to share my thoughts on a definition of API Craft. Deriving from the dictionary definition of craft:
"Skill in doing or making something, as in the arts; proficiency" and "The membership of such an occupation or trade; guild."
I suggest the following definitions of API Craft:
"An online forum for sharing and achieving proficiency in the skill and art of web API design, development and management" and "A physical gathering for discussion of the skill and art of web API design, development and management while enjoying a craft beer and good food."
Apigee has started something that has taken on a life of its own, becoming a powerful, community driven approach to evolving the skill and art of web API design, development and management--both on and offline.
I encourage you do participate, and I’d love to hear your definition of API Craft, as well as more information your local API Craft gatherings. I look forward to seeing you online and in-person at the API craft gatherings.
|API Craft, API Design, API Development, Apigee, OSCON, Portland|
blog comments powered by Disqus
Latest Blog Posts
- APIs in DFW
- Adding API Broker Under Monitoring for API Aggregators
- The Dark Matter That Make APIs Work
- Potential for API Aggregators to Provide Valuable Industry Data
- My Talk Tomorrow Night at the Dallas-Forth Worth API Professionals Meetup
- The White House Releases An Open Data Strategy
- When API Success Signals Begin Working Against You
- Get To Know Which Languages Your API Developers Are Using
- Twitters Developer Area is More Embeddable Than API
- Overview Of Backend as a Service (BaaS) White Paper
- Make Sure And Have Multiple KPIs For Your APIs
- API Enabled Toys For Our Children
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- How Much Do You Spend Attracting and Supporting Freemium API Developers?
- What Does The API Evangelist Do?
- Startups Need To Work Together on API Definitions
- Parse Is Successful By Truly Solving Problems for Mobile Developers
- API Commandment: Thou Shalt Not Forego Talking to a Person
- API Trends
- API Priorities
- Have You Taken A Look At AT&T APis Lately?
- Helping People Understand APIs Through Real World Examples
- Evolving Beyond API Service Providers and Tools to Goal Based API Toolkits
- APIs & The Federal Government
- After Last Couple of Weeks, It's Clear There Is Big Opportunity In The API Space