Hacker News new | ask | show | jobs
by Spixel_ 2 days ago
The studies you are talking about are probably outdated, it's difficult to deny the actual productivity boost of coding agents.

I'm not talking about the quantity of code produced, but about actual user needs that are now resolved that would not have been before.

The main productivity gain will not come from existing software engineer, but from people that couldn't code at all before but are now able to do things by themselves. We are still very early.

3 comments

It still takes the same mindset and skills to use AI productively and effectively as regular programming. The productivity boost only applies if you know what you’re doing and can actually steer the agent carefully.

Vibecoding hits a glass ceiling very quickly and this will not be solved incrementally. Besides, if the agent could work autonomously to that degree then it would no longer need any prompting at all and we’re living in a very different world. On the other hand that would make the debt actually meaningless, so I guess that is 'a' solution.

As a developer who has not been able to get any boost in productivity from coding agents, I find it incredibly easy to deny.

I’m a solopreneur, if I could lighten my load I would. However I have yet to save time using coding agents, with the exception of “I made this change to my model file, update all model to match the new format.” Which is cool, but maybe 0.01% of my job, and took a 1 hour task down to 10 minutes.

> The studies you are talking about are probably outdated, it's difficult to deny the actual productivity boost of coding agents.

Is it? Can you produce any evidence for such a productivity boost?

We previously had a backlog of 2 years of features planned. Now we have no work and are just working on tech debt and planning to get more involved in the product side because they need help getting the developers work to do.
I'm sure all your users would totally agree and will be head over heels about the slop you've pushed on them.