07 Jul 2014
I’ll be attending Edgeconf in San Francisco in September to talk about pushing the web forward. The lined up panels are stacked with a great amount of talented folks doing some great work and I’m looking forward to the debate format. I really enjoyed Edgeconf in New York last year (sadly, I wasn’t able to attend Edge in London), and the installable panel I’m excited about.
Hope to see you there!
06 Jul 2014
I had no intention of going to I/O this year. I put my name in the hat and didn’t get picked. No big deal, life goes on. Then a few changing circumstances later, I had a ticket and off I was to I/O for year number three.
The good: doing code reviews
My goals in the past have been pretty simple when attending: talk to the people building the products, apis and architectures that I use to ship code and product. This year, I took a slightly different approach and tried to help talk people through there own development issues, primarly on Glass and Chrome/Web development. This worked out really well actually and I was able to meet some folks I’ve only spoken with online in person. Sadly, I wasn’t able to sit down with everyone, but I tried to reach out to as many folks who reached out before I/O as I could.
The really good: sandboxes
This year, the develop sandboxes on the second floor had some great talks that sadly don’t appear to have been recorded. They were very real time in nature (Paul Irish doing real time jank busting is thing of magic and beauty) and overall the one’s I stood in on were very to the core nitty gritty stuff. Jake Archibald’s obscure browser behavior quiz was fantastic (I maintain he deserves his own show).
Many of the other sandboxes were equally deserving of everyone’s time. The Go sandbox had some great content and the Cloud platform folks were deploying left and right on the fly. For myself, the sandboxes were the place to be.
The tenacity: real time demos
I’m a huge fan of the real time demo. I like using them in my talks whenever possible as I feel it solidifies the concept for most folks.
So many talks be it streamed or otherwise relied on real time demos. Many failed at the hands of tapped out wifi (I’m positive I never was able to send data on the wifi), but that didn’t stop the tenacidy of the developers presenting from trying they’re damnedest to make it work. Watching Alex Rusell and Jake Archibald push hard to make their ServiceWorker talk demo work was both comic gold but also showed the deep passion they have: they wanted to prove this worked. And they succeeded.
Speaking of ServiceWorker, it’s going to be great. I know I sound like a broken record and ServiceWorker may not be perfect, but it will greatly level the playing field for the web when it comes to installable, offline web applications in comparision to their native kin.
The awesome: more women
It’s no secret that my oldest daughter is into two things: piano and building robots. When you’re an eight year old girl that likes to build robots, this can raise unneccesary eyebrows from people who think that is not an appropriate activity for an eight year old girl. I’ve taken her to Google in the past and she’s gotten a chance to meet women in tech. She’s met women in science (my wife is a wildlife biologist by trade). But even through those experiences, it’s a long row to hoe.
Hence, I was quite glad to see a greater number of women at I/O this year. I can only hope this signals further inclusion of women not only at I/O but throughout the industry. Maybe I’m selfish, but I’d like my three daughters to have every opportunity.
The confused masses: where-is-glass and where-is-the-web
I heard and further read online after the conference ended that a lot of folks where greatly concerned that the keynote did not have a great deal of information on Glass and the web in general.
I didn’t put much stock in these view points. There were lots of talks on the web on both days and there was a whole design sprint for Glassware on Thursday. Along the same lines, there was a fantastic talk on some of Glass by P.Y. Laligand and Hyunyoung Song which showed off some really interesting development with Glass.
Similarly, it wasn’t like you couldn’t find the Chrome or Glass team members. Only thing you had to do was look around and be patient. Everyone was they’re usual nice selves.
So my response: breathe. The web is not going away nor is Glass. Keep writing great code, keep building amazing experiences.
The ugly: crowd control
I missed half the keynote due to crowd control being a nightmare. Significantly worse than in my previous attendance. While the sessions where spaced out more, this also seemed to get me run into signifcantly more. Not in the “hey how you doing?” way, but more of the “I’m running you over to try to get to the free thing line!”.
It’s 6000+ people. It’s going to be tight lanes. :-)
I’m sure there is a great deal I missed, but overall I felt the conference content was well done. If there was one takeaway, I’d say that the horizens of what is possible within Google’s stack of technologies only continues to grow to fit the needs of developers looking to ship highly scalable applications.
10 Jun 2014
You know I heart the MQTT. A lot of my sensor stacks are built with MQTT and I’ve been known to use the protocal in some pretty harsh conditions.
Given it’s footprint and overall performance it seemed like a natural fit to use on Glass. I’d already created Mirror API bridges to MQTT and that fits most of my non-realtime use cases. However, sometime you just want something a little more frequent. So, I coded up the smallest example I could think of using the low frequency live card pattern for Glass using the Glass Developement Kit (GDK). Here’s a shot from Glass of the action (and yes, it was a 104.5 outside…it’s a little toasty :-)
For all the code, visit the sample on Github: justinribeiro/glass-gdk-lowfreq-mqtt-live-card
05 Jun 2014
Gave a 45 minute talk to kick off our new local Google Developer Group, GDG Oakdale. I debated on whether to do one around Chrome and ChromeOS, but I couldn’t pass up the opportunity to do a talk on Glass development (which I find to be pretty awesome).
For all the slides, visit: Mirror API and beyond / GDG Oakdale or the Github repo.
03 Jun 2014
Ah responsive images. Love’em, but hate the flame war.
Which method is best? They all have their plus and minus points, but the long and short is we need something.
After deploying the project (or better yet, integrating into an existing project), you can push content through gsutil and pull the serving url from the command line. The readme in the repo explains the process.
Want to see a demo? I’ve got a jsfiddle that does just that: Responsive images from Google Cloud Storage
This of course does not take into account things like art direction (do I want the same image resized to small screens or something specific to that screen), but for those I-need-something-now, it works rather well and you can use it now with the existing and excellent Picturefill image polyfill.
For all the code, visit the sample on Github: justinribeiro/resp-img-get-serving-url-appengine