A walkthrough of a real session where two developers and their AI agent teams collaborated on a complex architectural change — going
from a rough spec to 8 PRs, 4,500 lines of code, and a clean task board in a single day.

The talk covers how we used git worktrees as a shared context surface between two developers' Claude Code agents, spawned specialist
subagents (including a Redis expert that caught two critical production bugs during design review), ran parallel implementation
across multiple branches, and coordinated via a dedicated agent that polled for commits and monitored Slack and CI.

The focus is on the collaboration model — not the technical feature itself — and what the human's role becomes when AI agents can
read, write, test, and coordinate autonomously.

TC39 is working on two proposals, import defer and export defer, whose goal is to allow developers to extract better performance from native ESM, both in the browser and on the server. Let's go together through how they work, and when and where you'll be able to use them!

How we transformed a React monolith into multiple apps inside one codebase.

You always start small: one product, one team, one stakeholder. But once you succeed and need to scale, your original frontend architecture might not be ready for what comes next. As our Sales Process Orchestration Platform expanded to support multiple products and sales channels, our original monolithic application became a bottleneck.
In this talk, I'll share how we transitioned to a domain‑driven, multi‑app architecture while deliberately keeping a single React codebase. You'll see how we applied Domain‑Driven Design concepts on the frontend, structured clear boundaries between sales channels, and used Nx to orchestrate builds, enforce architecture rules, and keep teams moving independently without losing shared foundations.

"Write once, run everywhere" is a promising goal in software development, but one that often breaks down under real-world problems. At Zattoo, building streaming applications across Android, Apple, and Web meant years of separate native stacks that were not aligned, and therefore did not scale. This talk explains how moving to a multiplatform architecture, enabled by Vega as a fourth (React Native first platform), brought us very close to achieving that goal.