Productivity gains from AI coding assistants haven’t budged past 10% – survey
1–10 of 99 posts
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#2I think that over time people will start looking at AI-assisted coding the same way we now look at loosely typed code, or at (heavy) frameworks: it saves time in the short term, but may cause significant problems down the line. Whether or not this tradeoff makes sense in a specific situation is a matter of debate, and there's usually no obviously right or wrong answer.
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#3I can see where productivity could be higher if all I did was type in programs to some spec, or bootstrapping new apps all day - but that's like not the reality of "programming", at least for me past 25 years. Sorting through what to even make and interpreting "requirements" is what takes the most time
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#4Yeah, industry has told them that devs aren't valuable and AI can do their job. Who TF has motivation after that?
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#5You're only as fast as your biggest bottleneck. Adding AI to an existing organization is just going to show you where your bottlenecks are, it's not going to magically make them go away. For most companies, the speed of writing code probably wasn't the bottleneck in the first place.
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#6Yeah, industry has told them that devs aren't valuable and AI can do their job. Who TF has motivation after that?
[flagged]
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#7I found the title for this post misleading. To clarify it a bit, AI has only improved productivity by 10% even though 93% of devs are using it.
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#8I think that over time people will start looking at AI-assisted coding the same way we now look at loosely typed code, or at (heavy) frameworks: it saves time in the short term, but may cause significant problems down the line. Whether or not this tradeoff makes sense in a specific situation is a matter of debate, and there's usually no obviously right or wrong answer.
Once the free money runs out, the AI cos may shift to making heavily verified code snippets with more direct language control. This will heavily simplify a lot of boilerplate instead of fairytales of some AGI coding wiz.
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#9You're only as fast as your biggest bottleneck. Adding AI to an existing organization is just going to show you where your bottlenecks are, it's not going to magically make them go away. For most companies, the speed of writing code probably wasn't the bottleneck in the first place.
one thing that aways slowed me down was writing jsdocs and testing.
Now i can write one example of a pass and then get codex to read the code and write a test for all the branches in that section saves time as it can type a lot faster than i can and its mostly copying the example i already have but changing the input to hit all the branches.
Re: Productivity gains from AI coding assistants haven’t budged past 10% – survey
#10Blunt opinion: Most devs are not that good and really only execute what they are told to do.
The threat of AI for devs, and the way to drastically improve productivity is there: keep the better devs who can think systemically, who can design solutions, who can solve issues themselves and give them all the AI help available, cut the rest.