We turn high signal in-person events for the top AI engineers, founders, leaders, and researchers in the world into the best free learning opportunities for millions around the world here on YouTube. Your subscribes, likes, comments, speaking, attendance, or sponsorships goes a long way toward making our biz model sustainable indefinitely. We strongly believe this industry deserves a better class of community and that we know how to do this well; we just need your support.
I watched Google DeepMind's research chief explain why writing code is officially free, but there's a massive catch. We're about to drown in a wave of machine-generated software, and our current testing tools can't handle it. The solution requires a fundamental shift in how we design programming languages, and it won't look anything like Python.
I've been analyzing how an autonomous agent quietly dominated a major machine learning competition. It didn't win by throwing massive computing power at the problem, but by mastering a specific workflow. You'll see how human engineers are shifting away from writing code to designing the boundaries that guide these agents.
I've been looking at how top tier software companies are speeding up their model development cycles. It turns out that relying on engineers to monitor training runs is a massive bottleneck. They have figured out a way to let their models coach themselves and even coordinate their own training runs from a chat app, leaving human developers to focus entirely on high-level architecture.
I've been tracking how the top AI labs build their own tools, and a recent discussion with Anthropic's team exposed a massive shift in how they write software. They've built an autonomous assistant that integrates directly into their team chats and now lands over half of their product code. The secret isn't just better prompting—it's a complete rethink of how they structure developer permissions and codebase architecture.
I've analyzed why code generation is scaling faster than our ability to review it, creating a dangerous gap in software teams. I found a specific operational trap that causes teams to lose the thread of their own code bases, and it is not just about relying on AI tools. You'll learn how to establish a clear boundary of responsibility before your team surrenders its technical authority entirely.