The blog of Abraham Williams

On this nice sunny day I'm happy to announce that I will be joining the Twitter Platform team as a Developer Advocate. This is especially exciting for me as I have been thinking about developer communities a lot recently and can now officially start implementing some of my Unicorn Theories . I will also be acting as a voice representing the third-party community within the company and will be looking into pushing a few projects out the door. High on my priority list are: open sourcing Twitter for Android , increasing rate limits to 1500 requests/hour , launching a cleaner, simpler version 2 of the API , and opening Annotations to a wider audience. As I start implementing Unicorn Metrics I will be keeping a birds eye out for potential additions to the advocate team. If you are interested solving hard problems be sure to check out #jointheflock . All new employees get an awesome Twitter shirt! Stay tuned for news on Chirp 2 (Trust me! You are going to love it!), and be ...

Recently I presented a brand new presentation titled Please Feed the Unicorns at the @ apimeetup held at the @ Apigee office. The goal being to bring attention to various methods of building a better developer community around your API platform by empowering, incentivizing, and recognizing the community Unicorns. Please Feed the Unicorns from API Meetup on Vimeo . Please Feed the Unicorns View more presentations from Abraham Williams [<a href="http://storify.com/abraham/please-feed-the-unicorns" target="blank">View the story "Please Feed the Unicorns" on Storify]</a> Related articles Feb 23rd Open API Meetup: API Outlook for 2011 (apigee.com) Your API Sucks: Why Developers Hang Up and How to Stop That (apigee.com)

@ oneforty recently launched a QnA site where myself and several other Twitter developers are active. In September we launched answers.oneforty.com as a test to see if the community was interested in an additional medium to communicate and help one another as we all try to make the most of all the power of Twitter at its applications.

Draft! Not yet implemented. Please leave comments with your feedback. Historically my responses to inquiries has ebbed and flowed. Sometimes my inbox would pileup for a month before many people would get responses. This manifesto is my contract to the world to improve my communication response time. Before contacting me I suggest you read this manifesto and a couple of essays about email. Here is my commitment to response time going forward: Short form: - @Twitter*, SMS, @GitHub, IM, etc. - Response within 24 hours. - Must be less then 250 characters. - Preferred method of contact. Long form: - Email, @Facebook, snail mail etc. - Response within 48 hours. - Generally longer then 250 characters. - Keep it short and to the point. Voice: - Phone calls, voicemail, @skype voice, etc - Callback within 24 hours. - You must leave a voicemail. - I don't like phones so you should consider the above options first. What if I miss my deadline? If it is impo...