今日已更新 88 条资讯 | 累计 40862 条内容
关于我们

AI Made Coding Faster. Now the Bottleneck Has Moved.

Khanh Nguyen 2026年09月08日 23:41 2 次阅读 来源:Dev.to

The code is being produced faster than I can confidently review, validate, and ship it. Old workflow vs. new workflow The biggest change in my workflow is not simply that AI writes code faster. It is that my role is gradually moving away from manually implementing every detail and toward designing, orchestrating, reviewing, and validating the overall result . That sounds like a small shift, but it changes where I spend most of my engineering effort. Coding is no longer the slowest part Working with coding agents has changed how I think about development productivity. I can define a task, let an agent explore the codebase, implement the change, add tests, and return a working diff much faster than I could build everything manually. But implementation is only one stage of software delivery. flowchart LR A[Requirement] --> B[Design] --> C[Implementation] --> D[Review] --> E[Test] --> F[Deploy] AI can compress the implementation stage dramatically, but review, testing, integration, security, and deployment still have their own limits. When those stages cannot keep up, faster coding does not remove the bottleneck. It simply moves it downstream. This is also the point Red Hat recently raised in Why faster coding isn't making delivery any faster : generating code and delivering reliable software are not the same thing. I have started to notice this more clearly in my own workflow. An agent can produce a fairly large change while I am still building the mental model needed to judge whether that change is actually good. More code is not the same as more productivity Suppose I used to complete two meaningful changes in a day and AI now helps me produce six. Calling that a 3x productivity increase sounds reasonable at first, but only if the rest of the engineering system can absorb those six changes. They still need to be understood, reviewed, tested, integrated, and eventually operated in production. If review capacity or CI becomes the constraint, I have not created three ti

本文内容来源于互联网,版权归原作者所有
查看原文