Posted on 01-23-2013
I love to write. My girlfriend has really help me kindle this passion. Thank you @audreywatters.
After 2.5 years of telling stories on API Evangelist, I’ve gotten pretty good at organizing my ideas, and putting out stories that showcase the best (and worst) from the Business of APIs. I’ve gotten so efficient at it in 2012, I even launched API Voice which is dedicated to the politics of APIs, the API Stack which is dedicated to top APIs and Hack Weekends which is all about hackathons.
When I meet people in the real world, I often hear, “You sure blog a lot, I see like 5 posts a day coming from you!” I do write a lot, but it comes in waves. I tend to write a lot of stories all at once, pumping out 15-20 pieces and then I trickle them out across the appropriate domain over the next couple days.
In 2013, I’m going to get even more efficient with my storytelling, with an evolved approach I’m calling Hacker Storytelling.
The process is based upon dwhat I already do, but uses a new blend of:
- Pages - HTML, CSS and text that frames a site, project or research
- Blogs - Chronological blog posts that walk through a project or research
- Presentations - Deck.js presentations that walk through a project or research
- Data - JSON, XML or database stores that drive the essence of a story
- APIs - Simple, data and representations derived from APIs
I use these formats to tell stories across my blog, but in 2012 I learned some new techniques with existing and new technology that I have discovered, and will be employing a series of technologies that help me better deliver stories:
- Jekyll - Jekyll is a simple, blog aware, static site generator. It takes a template directory (representing the raw form of a website), runs it through Textile or Markdown and Liquid converters, and spits out a complete, static website.
- Mustache Templates - A simple way to render structured data from JSON files, using basic HTML templates for displaying--instead of pulling directly from database.
By default all of my projects start as a Github repository with a base Github Pages + Jekyll implementation I’ve setup for my API Evangelist brand. This will force me to be open and transparent by default. I know this reality isn’t meant for everyone, but for me, I hate seeing many of my projects never leave the firewall and end up being deleted from an Amazon EC2 instance in the dungeon of my IT network.
All my projects will become Hacker Storytelling projects. Some will have a single page, while others will have blogs, presentations and simple or complex data driven tools that help support the story.
Currently I have four projects who live in this new format and are hosted entirely on Github:
My goal is to be open by default, when it comes to content and data and make sure I share all of my ideas, in the widest and most shareable and remixable way possible. My objective during my time on earth is to tell stories and write code that will make change, no matter how small.
I believe that Hacker Storytelling will help me do this! I hope it will help you too!
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API