Loading video...

Video Failed to Load

Go Home

AI coding tools increase developer output. But growing pull request backlogs can easily overwhelm engineering teams, contributing to what’s known as “review fatigue.” Here’s how to calibrate your workflows for agentic development. Improve prompts, use stacked pull requests, and recognize how the developer role is changing.

11,426 views • 5 days ago •via X (Twitter)

1 Comments

Madeactual's profile picture
Madeactual4 days ago

The bottleneck is not output; it is review bandwidth. If AI doubles PR volume without changing ownership, test depth, and merge policy, the “productivity” metric is just work sitting in a queue.

Related Videos

New course to bring you up to state-of-the-art at using AI to help you code: Build Apps with Windsurf's AI Coding Agents, built in partnership with WIndsurf (Codeium) and taught by Anshul Ramachandran! AI-assisted IDEs (Integrated Development Environments) make developers’ workflows faster, more efficient, and much more fun. Agentic tools like Windsurf are more than just code autocomplete—they are collaborative coding agents that help you break down complex applications, iterate efficiently, and generate code that spans multiple files. Although a lot of coding assistants share the same underlying large language models for planning and reasoning, a major point of distinction is how they handle tools, keep track of context, and stay aligned with your intent as a developer. For instance, if you make modifications to a class definition in your code and make the same modifications to other classes in the same directory, you might tell the AI agent "Do the same thing in similar places in this directory." Here, tracking your intent means understanding that “the same thing" refers to that recent edit you just made, which must be followed by appropriate search and tool-calling to implement the changes. In this course, you'll learn the inner workings of coding agents, their strengths and limitations, and how to use Windsurf to quickly build several applications. In detail, you'll: - Build a mental model of how agents work by combining human-action tracking, tool integration, and context awareness to carry out an agentic coding workflow. - Learn the challenges of code search and discovery and how a multi-step retrieval approach helps coding agents address them. - Use Windsurf to analyze and understand a large, old codebase and update it to the latest versions of the frameworks and packages it uses. - Build a Wikipedia data analysis app that retrieves, parses, and analyzes word frequencies. - Enhance the performance of your Wikipedia analysis app by adding caching, and through this, also learn how to course-correct when the AI agent produces unexpected results. - Learn tips and tricks such as keyboard shortcuts, autocomplete, and @ mentions to quickly call on agentic capabilities. - Use image/multimodal capabilities of the AI agent to increase your development velocity; you'll see an example of uploading a mockup with sketched-out UI features, and ask the agent to use that to build new functionality to an app. By the end of this course, you’ll understand agentic coding in-depth and know how to use it to make your development process much faster, more efficient, and enjoyable. Please sign up here!

Andrew Ng

140,162 views • 1 year ago

GitHub has a front-row seat to how code is changing now that everyone—and their army of agents—can ship code. In March alone, agents created 17 million pull requests on the platform. That’s why I was thrilled Mike Taylor was on hand to interview GitHub COO Kyle Daigle at Microsoft Build for a behind-the-scenes look at how the platform is helping developers manage the influx without dictating which pull requests they should trust or merge. This week on Every 🪨’s AI & I, Mike gets into: - The 14x commit explosion. GitHub hit 1 billion commits last year. Kyle says they’re on pace for 14 billion this year—and he doesn’t think that curve is plateauing. - GitHub is committed to letting open-source maintainers set their own standards. Agent PRs are flooding communities, but GitHub’s philosophy is to leave code maintainers in control. - The developer/non-developer distinction is collapsing. GitHub’s own legal and finance teams are using Copilot to build apps, one example of how AI has expanded the definition of who counts as a developer. - Per-seat pricing doesn’t survive a world where agents run while you sleep. Kyle thinks automatic model routing—swapping in Haiku for simple tasks instead of always calling the expensive model—is the best way to make the economics make sense. - Daigle runs a daily self-improvement loop with an AI he named Baxter. Every day, Baxter reads 7 days of his emails and Slack messages, flags his communication patterns, and checks whether Kyle followed last week’s advice. This is a must-watch for anyone running agents in their dev workflow—and curious how GitHub is handling the explosion of commits on its platform. Watch below! Timestamps: Introduction: 00:00:52 The agentic PR flood: 00:03:27 GitHub’s approach to helping open-source maintainers manage the surge: 00:04:33 What 14 billion commits means for code quality: 00:06:15 Moving from per-seat licensing to usage-based pricing: 00:08:03 Kyle's dual role as GitHub COO and Microsoft's chief marketing officer for developers: 00:09:45 Developer choice as competitive moat: 00:13:03 How to balance dogfooding your own tools with staying honest about the competition: 00:14:57 Hill climbing, frontier tuning, and solving the model-routing problem: 00:19:45 Kyle's agentic communication hack: 00:24:45

Dan Shipper 📧

18,569 views • 3 months ago