OpenAI Build Week Community Event - Tokyo

I had the honor of joining a Codex hackathon.

OpenAI Build Week, a full-scale global hackathon, is running right now, and this was its Tokyo community event — about seventy Codex fans in one room. A community where everyone has something they want to make is a comfortable place to be. The premise isn’t “let’s think about it together” — you build solo. Even in groups, it’s more like loose mutual feedback.

Between planning, building, and iterating, the three hours vanished. A hard deadline, and the faint sting it brings. It had been a while. The young builder next to me let me watch, up close, how he worked. He got something running early and spent the rest of the time improving it — a very efficient way to build. Me, on the other hand: I’d written up the spec I wanted as a brief for Codex, which was fine, but then I threw the whole build at it at once. Frontend and backend both went into motion, and I ended up waiting forty minutes. I learned the hard way how much it matters to ask for a minimal working experience early and fix it from there.

Watching the presentations, a surprising number of the projects existed simply because the builder wanted them. Not built to scale — requested because you want it now, and out it comes. Less “a product you keep using” than a tool that resolves the need right in front of you. It’s fascinating to watch this become a layer of interface, like operating a mouse.

The flip side: to raise something to product quality and maintain it, leaning on Codex alone probably won’t be enough. I was reminded how little experience I have. It made me all the more curious how the people who ship polished products — on large teams or as solo developers — actually build and manage them.

Everyone seemed to be itching to share what they’d made and get feedback, but between the headcount and all the solo builders, only a few got to present. That felt like the most improvable part. Watching the top flash talks, switching presenters seemed to eat as much time as the demos themselves — reconnecting screens, handling hiccups. Shorten that, and more people get to present.

Maybe something like this?

• An HDMI switcher (an ATEM Mini) plus a preview monitor showing what’s connected, so the next presenter is plugged in and checked ahead of their turn
• Hard 90-second demos with forced switchover, and a timer visible to both presenter and audience
• The moment presenters switch, the next person in line starts setting up

Some setups won’t fit in 90 seconds, but it might smooth things out. Whether many people get a chance to present and receive feedback seems to be what drives satisfaction — that’s the kind of community it looked like.

It had been a long time since I’d worked my head that hard, and I slept on a pleasant kind of tired. I’d been starving for stimulation, so an occasion like this is a real gift. My thanks to the organizers, the participants, and the sponsors.