
My Dot took care of demo week
posted
I worked on the dots live demo. Holly did a phenomenal job on stage today. If you've ever been there, you know the pressure is immense. She handled the recovery SO well. I flew to SF from Singapore for my 4th DevDay (and first an OAI employee). It's been a joy to get a small glimpse of what the dots team has been cooking. Truth be told, I was slightly skeptical of using dots when it was first introduced. I was already really comfortable using Codex and setting up plenty of automations. I wasn't sure how much more I'd get out of it. But a few personal examples that I can share publicly changed my mind. 1. En route to SF last week, my rideshare cancelled on me. There was the generic automated refund email. My dot immediately picked it up, knew I had a flight, and asked if I was okay. 2. During this trip, after days of DevDay prep, I woke up and told it, "Fuck my life, I'm so tired - what's on my cal today." It walked me through my day, then added one last thing: "Please take some time to eat and drink. Take one step at a time - you got it". Alone in a hotel room, that felt really reassuring. 3. On the building side, I've been using dot to spawn Codex threads that use CUA and ultrafast, and to proactively scan PRs for changes that might affect the demo. It's been useful for getting work done, and increasingly insightful and high-signal in ways I hadn't expected. I could delegate more confidently without repeating the same context for the umpteenth time. 4. Even this post came together with my dot, as I spoke to it throughout the day to investigate what happened and emotionally process it. Hope you give it a shot and see what I mean :)
First-hand from OpenAI employee Gabriel Chua (he worked on the Dots live demo): skeptical at first, his dot then (1) caught his cancelled rideshare's refund email, knew he had a flight, and checked on him; (2) walked him through his day when exhausted and added a caring note; (3) proactively spawned Codex threads and scanned PRs for changes affecting the demo; (4) helped investigate the day and co-write this post. Disclosure: author is an OpenAI employee posting personal first-hand use.
