A couple of months back I presented at IBM Interconnect about developer events and why they’re increasingly important. IBM is a client and paid my travel etc.
Some of the reasoning is fairly obvious. Twilio for example, is now adding $1m in annual recurring revenue every seven days, driven by participation in more than 500 developer events in 2014.
IBM itself has been investing heavily in developer ecosystems, events and locations, through its Ecosystems and Digital Cities initiatives. It’s been running tons of BlueMix (IBM’s Cloud Foundry implementation) training events, hackathons and so on. And of course it supported the Shoreditch Village Hall venue, by Shoreditch Works, helping to fund a space in which we ran developer community events and conferences such as London Node User Group, London Java Community, and Cleanweb throughout last year.
But for traditional companies, IBM’s core customer base, the obvious isn’t always so obvious, so I put together this deck to help IBM clients (and Big Blue holdouts) understand the value of face to face interactions with developer communities, but also to provide some advice about how to come across.
So here are some dos and don’ts. I bet you have your own pet loves and hates. Please make your own suggestions.