Head of Developer Experience & Relations at Hookdeck
Inspired by the first two talks at stacked13 by Mike Taulty and then Maarten Balliauw I thought I'd jump straight into Windows Azure Mobile Services and build an a realtime collaborative synchronised todo list . I'd do this based on the Get started with data in Mobile Services HTML guide . I would then and host it on a Windows Azure web site .
First I'd like to emphasise that this is a blog post on how and not why . The why comes down to the judges. So, thanks Judges! Secondly I'd like to thank Rob Dunfey for the idea and for providing additional motivation - I'll dig deeper into this later. Finally: what am I going to cover? As the title suggests, I want to cover the how .
For a long while now I've not been getting as much out of Twitter as I used to. There's too much information to take in. I've long said that Twitter is throw-away. If you miss something then it doesn't matter. If it's important then I'll see a retweet or pick up the information from somewhere else. This is wrong . Just because it's not being retweeted by everybody it doesn't mean it's not a worthwhile update. Just because it doesn't get upvoted on Hacker News it doesn't mean that it's not relevant to me.
I'm on the What Developers Want panel at the Business of APIs Conference London, arranged by Mashery. I'm also giving a lightening talk on my take on What Developers Want. Unsurprisingly I believe they wany the APIs to offer access to their data in Realtime. Here are the details.
A couple of days after the WebSockets panel at HTML5DevConf in San Francisco I gave a talk at TwilioCon. We were asked to try and cover a big topic and focus on a few key points. Since the conference was for Twilio, a telephony cloud service, we want...
On October 16th 2012 I sat on a HTML5DevConf WebSocket panel along with Ilya Grigorik from Google, Matt DeBergalis from Meteor and Peter Moskovits from Kaazing - the panel was chaired by Frank Greco , also of Kaazing.
It's too broad a statement to say that absolutely everybody is your customer. But, you actually never know if the next person you speak to could be a potential customer so you should treat them that way. Treat them the way you would want to be treated no matter the roles you are currently in. Let me explain.
I can't believe it! I left University to take my first job 11 years ago. During that time I've worked in finance, e-learning, GIS and SEO/digital marketing. Although I've had some interest in these sectors my real interest was just the technology, with a passion for realtime web technologies. I now work for Pusher and can focus almost entirely on realtime web technologies and the application of them. Whilst I'm truly lucky to be able to work day-in day-out on something I'm passionate about, it's always a good idea to gain exposure to new things. New experiences exercise the mind and you never know when those experiences will help with what you normally do.
A couple of weeks ago I attended HackLDN for the 2nd time. The focus of the event is very much to create something with real business potential. I completely understand the reasoning behind that and back the idea. But, if everybody had an idea and everybody wanted to work on their own project, to create a company, then there would be a lot of one-man/woman teams. We need people to go along to have fun and experiment with technologies. These types of people are as important as the 'entrepreneurs'. I decided to pitch Bring Back Beckham (redux) as a fun experiment - not a startup idea. And low and behold I ended up with a team.
I'm attending Hackathon London this weekend. Normally I help each team at the event but don't get too involved in individual projects. This time things might be different. In 2006 David Beckham was dropped from the England squad by Steve McClaren. This wasn't a footballing decision, it was to try and stamp his authority on the team and show he was his own man. It massively backfired.