TADS Maturing and Flourishing

16/09/2014

Developers delving into telecom? How about taking a trip to Istanbul?

201409-tads-banner

I’ve been following Alan Quayle for many years now. He has a great blog covering the telecom space. Last year, he set out on a new journey – to create a community of telecom developers. Something that existed, but had no home. That’s how TADSummit got created: a place for Telecom Application Developers.

First event had around 100 people – all converging in Bangkok – not your usual conference place for developers. In June, the TADHack took place in multiple physical sites and virtually. This event had close to 500 participants.

This year, TADSummit takes place in Istanbul, and will offer some interesting tracks covering topics anywhere from go to market and innovation to managing intellectual property.

As TADSummit matures, it seems to be flourishing. The agenda has changed from last year, and instead of two separate tracks running through the 2 days of the summit; this year most of the content will be available in a single track, with breakout sessions that then gets summarized to the whole forum. Another new introduction to TADSummit is the keynotes – a successive set of 7 rapid fire keynotes – each limited to 10 minutes. This timeframe should get the keynote speakers focus on what they have to say instead of boring the audience with marketing material (the usual result of keynotes in our industry).

Alan did a great job at designing this event. I do you you are booking your tickets to Istanbul on the 12-13 November. While I won’t be able to make it there, the roster of speakers is impressive, and should give you ample reason to join.

Responses

Michael Graves says:
September 17, 2014

Alan Quayle and a cast of TADsters will be making a guest appearance on this weeks VoIP User’s Conference call (http:///vuc.me) to discuss the coming TADSummit. Moreover, we’ll be hosting the call on Jitsi Video Bridge as has been our habit in recent months. Leveraging a bone fide WebRTC approach only seems appropriate.

Reply

Comment