Chapter 07 / 20
7. Flow & Developer Experience: Where Did the Queue Move?
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
Imagine an illustrative change finished at noon. It waits for review until the next morning, for an environment until Thursday, and for a cross-team approval until Monday. Reducing authoring time from four hours to two would barely move the customer's date. Adding more changes to that queue may move it in the wrong direction.
Salesforce describes rising code volume and review latency after AI-assisted development accelerated code creation. It names human reviewers and larger PRs as constraints. Its report does not publish a ledger of additional hours by reviewer or prove the downstream customer effect. That limitation is exactly why an engineering leader should follow arrivals and waiting at each stage, not merely celebrate local speed.
Two approaches can improve flow. One makes the authoring step faster: an assistant drafts repetitive code, migration scripts, or tests. The other changes the system: smaller batches, a reliable CI pipeline, clear review ownership, earlier detection of common problems, and low-risk approvals that do not wait unnecessarily. A third often matters most—choosing fewer changes with clearer value. The best approach is the one that improves end-to-end time without overloading the people who verify and operate the result.
Do not confuse ease of work with absence of effort. The Microsoft-led field experiments report more completed tasks in the pooled comparison among developers given a coding assistant. They did not measure an equivalent lift in customer outcomes. The SPACE framework likewise cautions against using activity alone as a measure of developer productivity; satisfaction, performance, collaboration, and flow matter in different ways. Neither source says that every engineer should use a tool on every task.
A useful flow map has two kinds of time: active work and waiting. Record PR arrival rate, review age, time to first meaningful review, CI failures, rework, release lag, and customer time to use. Segment by size and risk. Ask reviewers about cognitive load, not just their average response time. An AI review pass may save effort or add another layer; test which.
At the junction: Follow five similar changes from a named customer problem to verified use. Point to the largest queue and the team that owns it. Do not fund a speedup upstream without a credible plan for the work arriving downstream.
Sources cited in this chapter
- https://engineering.salesforce.com/scaling-code-reviews-adapting-to-a-surge-in-ai-generated-code/
- https://www.microsoft.com/en-us/research/publication/the-effects-of-generative-ai-on-high-skilled-work-evidence-from-three-field-experiments-with-software-developers/
- https://queue.acm.org/doi/10.1145/3454122.3454124