What happens when AI agents start relying on the same messy docs your team already struggles to search? Demetrios hops into a Waymo in San Francisco with Dave Nuñez, founder and CEO of Falconer and co-author of Documentation for Developers. They talk about why developers and agents need different things from docs, why agents sometimes skip up-to-date instructions, and how a stale internal document can contribute to a production incident. Dave shares how Stripe cut roughly 500,000 internal docs down to 5,000 worth maintaining. The conversation also covers how to capture the reasoning behind engineering decisions, when a diagram beats a wall of text, and who owns the fallout when an agent acts on bad information.

Are you paying attention? Software engineering has changed. Agents are here in force. Everything is in flux. To adapt in the long term, we must understand the foundations. An open-weight model took Svetozar Miučin's naive PageRank in C from 4 seconds to 0.1 seconds in about five minutes. He spent six years of his PhD building tools for that kind of work. In this talk, given in a personal capacity, Svetozar argues that inside every engineer are two and a half wolves. The builder wolf ships anything for the dopamine. The craft wolf cares about engineering excellence. The cub, the half wolf, decides what is worth building at all. Along the way, he covers why "we get paid for an outcome, not a verb", the shaky base of the engineering pyramid as fewer juniors come in, why the first question should be "can I sell it?" (get a letter of intent), and why the future is polymathic.

Agents write the code. Who builds the place it runs? Everyone is building software factories: agents triage, implement, verify, and ship. Google reports 75% of new code is AI-generated, and Uber attributes over 70% of pull requests to agents. But every one of those changes still needs somewhere to run, and in most companies that somewhere still arrives through a ticket. Code got cheap. Environments did not. Max Körbächer introduces the Infrastructure Factory: a platform that turns intents from humans or agents into compliant, owned, observable, cost-attributed environments, with no ticket in the path. He looks at why the most-cited software factory talks of 2026 call infrastructure the hardest part but none treat it as a factory of its own, how it relates to the AI factory and where the two share a floor, and what the factory looks like when its front door is an MCP server, and its policy gate is agentgateway. The target: zero tickets.