Skip to main content

DeveloperWeek 2017 and a trip among Bay Area developers


I recently had a chance to present at DeeveloperWeek conference in San Francisco. According to DeveloperWeek, it is the largest developer conference with 8000 attendees and hence I was pretty excited to represent and present Mozilla and talk about WebVR there.

The conference took place in Pier 27. I had never been to a pier before so it was little weird to find actually a full blown conference building in a pier. My talk was on the second day of the conference and at 9 A.M slot (I really hate morning slots). That gave me chance to go around the conference and look at other talks in the first day, also roam around the expo, talking to different people getting an idea of the audience. I couldn’t quite justify the 8000 developer claim, but the conference definitely was big, sprawled on two floors. They had it divided among topic categories, my talk was part of the VR & AR section. But in real physical location it did not seem to make much difference. The talk’s were being held in specific stages which were sprawled among the very big open space and in between having different booth of companies.


Though this setup allowed a lot of people to notice the stages, it also meant that there was enough ambient noise to interrupt the talk if you had too much audio-visual. I noted this and also marked out where I was supposed to deliver the talk, Pavilion 3 which turned out to be a big room in itself and I felt a little relief that I will not get interrupted by ambient noises. Which, was not really true.
On the day of talk, I decidedly started early. At 7:15 to reach much before time (for a change). I was staying across the bridge, and decided even if I consider the traffic on bay bridge I still should be able to reach by 8, considering Lyft and Google Maps showed me it as a 20 minutes distance. How wrong I was. So after some frantic texts between me and the space wrangler where she kept assuring me they will handle the space for me if I am late, I managed to barely reach the venue at 8:59 AM. So much for me being early. While getting out of my Lyft and dashing for the venue, I heard a familiar voice calling my name. That was Michael! He came all the way from Mozilla Mountain View office to attend my talk! A minute or two later when I was plugging in my laptop for the talk I also saw Sandra from Mozilla SFO to enter the pavilion for the talk. I was so happy and that worked as a confidence booster for me.
Just after the talk
undefined
I eventually started the talk mostly on time and it went great including most of the demos (I need to come up with a better way to show that spotify demo). Sandra was so kind to snap a few pictures of me.


Later that day I was catching up with the people who attended my talk and I realized the prevalent concern among the VR netizens were
  • Lack of way to traverse form a VR scene to other one (Resource)
  • A way to find and discover reliable and reusable components for Aframe (A-Frame Registry)
  • Concern about cross platform (Resource)
  • Questions regarding browser compatibility and how to keep up to date (webvr rocks)

I have hyperlinked the resources with the questions above which will take you to the answers I generally provided them.

One general opinion was that since most of my demo’s were geared towards mobile in Google Cardboard, I could only talk about the interactive demos, but couldn’t actually show them. A suggestion I plan to address in at least some of my future talks.
And that’s how I wrapped up the DeveloperWeek 2017. Of course I hanged around at the pier a few more hours to get a shot of how the city looks from the pier.





And how can my trip get completed without once going to Mozilla SFO office and meeting with Diego, trying out some Mozilla VR gear and having a sneak peak at A Saturday Night in WIP mode. It will very soon be released and you can have a blast at that time!
Me with Diego on top of Mozilla SFO office

Popular posts from this blog

Racecraft (Project Koru) · Prologue — The Origin Story

Racecraft · Prologue , The Origin Story It Started With a Wine List and a Question About Racing How a happy-hour conversation in the Bay Area turned into a trustable AI race coach , and then into a second version that runs entirely on a phone, on the NPU. This is the prologue to a five-part series. Two years ago(1st November, 2024) I was in the Bay Area for a GDE Summit. If you've never been: it's a couple of days of talks among Google Developer Experts, the kind of people who get unreasonably excited about a new on-device runtime, and then , mercifully , a happy hour where everyone stops performing and just eats. We ended up at a restaurant(Puesto Santa Clara), a long table of GDEs, and I was doing the most important engineering of the evening: trying to decide which wine to order. Across the table was Ajeet Mirwani . I don't even remember how the wine talk turned into racing talk , these things drift , but the moment the word "racing" ...

A Split‑Brain Neuro‑Symbolic Training Method for High‑Velocity Autonomous Coaching from Telemetry

 Author: Rabimba Karanjai Scope: Problem statement + data methodology + model training (no deployment discussion) Abstract Real‑time coaching in motorsport is a safety‑critical learning problem : a system must map noisy, high‑frequency telemetry to short, actionable guidance that remains physically consistent and avoids hazardous recommendations . This paper proposes a “Split‑Brain” training formulation that separates (i) a semantic coaching target (what action/critique should be expressed) from (ii) a reflexive interface (how actions are represented as compact, verifiable tokens). The approach trains a Small Language Model (SLM) in the Gemma family [1] using QLoRA fine‑tuning [2] , and introduces a telemetry tokenizer plus teacher‑student synthesis pipeline to generate instruction‑action pairs at scale. Core contribution: a reproducible method to convert “ golden lap ” differential tel...

My Friend's MRI Didn't Come with a Manual, So I Built One with AI

Gemma 4 Good Hackathon · Impact Track · Health & Sciences It started with two envelopes. One contained a single sheet of paper, a radiologist's report for my friend. It was a wall of text that might as well have been written in another language. Words like " parenchymal volume ," " hyperintensities ," and " susceptibility artifact " stared back at us, creating more anxiety than they resolved. The other was a flimsy paper sleeve containing a CD-ROM. This, we were told, held the actual images from her MRI scan. The ground truth. And we couldn't even look at it. Our laptops, like most these days, don't have disc drives. For a moment, this crucial, deeply personal piece of her health information was a coaster. I felt that familiar, hot-wired frustration every engineer knows: the feeling of being locked out by a dumb problem. The powerlessness was infuriating. So, I did what any slightly obsessive software engineer would do...