Developer Think Tank » heroku http://developerthinktank.com Issues and insights from developer program leaders. Thu, 16 May 2013 04:34:24 +0000 en-US hourly 1 http://wordpress.org/?v=3.4.2 Details: One Concurrent Visitor http://developerthinktank.com/roundtable/details-one-concurrent-visitor/?utm_source=rss&utm_medium=rss&utm_campaign=details-one-concurrent-visitor http://developerthinktank.com/roundtable/details-one-concurrent-visitor/#comments Wed, 09 Nov 2011 05:44:00 +0000 Tyler Singletary http://www.obliqueapi.com/?p=15

Look closely at the most embarrassing details and amplify them

A famous Ouroboros

This strategy ought to be attacked outright: like a ouroboros, I should present some embarrassing detail of my own. Since starting this blog, I’ve moved it from WordPress.com to a self-hosted install of WordPress.org, by way of Heroku. This was actually a great exercise in patience and tolerance.  Being able to treat the blog install as a software package, managed under git, with each new plugin and major change a commit, pushed and adapted to Heroku’s Cedar Stack.

This process happened over the course of… well, Sunday to Tuesday. Now that I’m on a self-hosted WordPress, I can run Google Analytics and watch those awesome pageviews come in. Even more entertaining since Google added Real Time Analytics.

Extra Amplification: That's not my image.

Why pretend you have traction you don’t?  Add an endpoint to your API that exposes your own analytics, even the embarrassing ones.  Integrate into your change management or bug tracker and expose the number of known issues.

 

]]> http://developerthinktank.com/roundtable/details-one-concurrent-visitor/feed/ 0