←back to thread

Survey: a third of senior developers say over half their code is AI-generated

(www.fastly.com)
214 points Brajeshwar | 2 comments | 31 Aug 25 14:55 UTC | HN request time: 0.558s | source
Show context
manoDev ◴[31 Aug 25 15:53 UTC] No.45084137[source]▶
“AI” is great for coding in the small, it’s like having a powerful semantic code editor, or pairing with a junior developer who can lookup some info online quickly. The hardest part of the job was never typing or figuring out some API bullshit anyway.

But trying to use it like “please write this entire feature for me” (what vibe coding is supposed to mean) is the wrong way to handle the tool IMO. It turns into a specification problem.

replies(3): >>45084676 #>>45088106 #>>45089397 #
1. Gigachad ◴[31 Aug 25 23:41 UTC] No.45088106[source]▶
I find this half state kind of useless. If I have to know and understand the code being generated, it's easier to just write it myself. The AI tools can just spit out function names and tools I don't know off the top of my head, and the only way to check they are correct is to go look up the documentation, and at that point I've just done the hard work I wanted to avoid.

Feels like a similar situation to self driving where companies want to insist that you should be fully aware and ready to take over in an instant when things go wrong. That's just not how your brain works. You either want to fully disengage, or be actively doing the work.

replies(1): >>45088327 #
2. platevoltage ◴[01 Sep 25 00:28 UTC] No.45088327[source]▶
> The AI tools can just spit out function names and tools I don't know off the top of my head, and the only way to check they are correct is to go look up the documentation, and at that point I've just done the hard work I wanted to avoid.

This is exactly my experience, but I guess generating code with depreciated methods is useful for some people.