Any tips on how to secure a ticket or invite so we're not left battling website bugs at the last second? I've been able to go twice but lack of information and a less-than-ideal sign-up process has made it difficult to ensure a way to secure a seat despite that. I'd think that previous attendance would be an advantage since it demonstrates how serious one is about networking with others and training on Google products.
My company has already agreed to give me the time off, buy the ticket, and fly me. Hey +Google Developers
, did I mention that we are a significant, up-and-coming player in the educational field and we're using Google tech more by the day? ;) It would be a shame if we didn't get every edge-up possible (especially those we're prepared to pay for) that would result in us using Google services.#io13
We realize that many won't get a chance to go and perhaps you've decided that it's "more fair" to withhold the knowledge, but I think I speak for most here when I say that we'd just like to know what to expect so our want/need/seriousness will give us the best chance to prepare rather than having to scramble at the last moment. #ifihadglass
I'd have one more reason to go to I/O. In addition to all my business interests and needs relating to Google, i'll be looking to invest a serious amount of time developing #Ingress
companion services for glass that will use position to poll for nearby enemy portals and resonators when within striking range of a portal. I'd also like to develop an Ingress location sharing server that helped active players (while active) identify others using glass.
Also, we're getting tired of the scalability issues inherent to SQL and .Net but rather than adapt for Azure, I want to take a good hard look at Apps and talk to other professionals who have. Once again, I have a business (and now personal) need for I/O and anxiously await a change to purchase a ticket.