Menu

1 / 4

Why the one-month feature doesn't ship in two days with AI, and what I do about it

DEV Community: career·Neilton Rocha·1 day ago
#S7LMLnxt
#devtocareer#devto#dev#agent#code
Reading 0:00
15s threshold

The request I hear most often now goes like this: a feature that used to take a month, and someone wants it in two days, because "the AI writes the code now."

It isn't only the people I work with. A developer on r/cscareerquestions asked other engineers how much AI had really sped them up, and put it plainly: "i don't think the 2x, 5x, 10x productivity gains leadership expects from us are actually possible at this point in time." The thread has more than 50 replies, and they don't agree on a number.

I use coding agents every day and I like them. They do type faster than me. But the month was never mostly typing. Most of it went to keeping the code in a shape the next person can work with, and that part didn't get faster. In some places it got harder, because the agent produces more code for me to keep in shape. This post is about where the month goes now that typing is cheap, and the checks I added so the agent stops bending the architecture.

1.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.