10 technical talks I’m excited about at GitHub Universe 2026

Let’s be real: “I’m excited about these talks” is GitHub’s polite way of saying “here’s the stuff we desperately need you to care about.” And honestly, they picked the right anxieties. Verifying AI-written code is the elephant in every sprint planning meeting right now. We’ve all merged a pull request that *felt* right, only to discover the AI hallucinated a dependency that doesn’t exist or, worse, introduced a subtle logic bug that passes tests but breaks production at 2 AM. A talk that actually addresses verification — not just “review your PRs, folks” — is worth the price of admission. The fact that it’s on GitHub’s own stage is telling: they know the tooling has to evolve beyond “here’s a code suggestion, good luck.” The npm dependency session is the other half of the same coin. We’ve spent a decade bolting security scanners onto a supply chain that’s fundamentally held together with duct tape and semver optimism. One compromised maintainer account and your entire build pipeline is suddenly mining crypto or exfiltrating env vars. GitHub positioning this as a headline topic isn’t just good PR — it’s an admission that the ecosystem they helped popularize has a trust problem that’s only getting worse as AI accelerates the rate of code production. More code, faster, from less-verified sources: that’s the nightmare scenario, and it’s happening in real time. What’s missing from this teaser is the hard part: the trade-offs. Verifying AI code at scale means either more compute, more human review, or more automated guardrails that could slow everyone down. Securing npm means breaking backwards compatibility or forcing migration pain on millions of projects. These talks will be great if they acknowledge the cost. They’ll be typical vendor fluff if they pretend it’s all solved with a dashboard and a cheerful blog post. Source: [The GitHub Blog](https://github.blog/news-insights/company-news/10-technical-talks-im-excited-about-at-github-universe-2026/)