←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.032s | source
Show context
lpapez ◴[31 Aug 25 21:31 UTC] No.45087294[source]▶
This article goes completely against my experience so far.

I teach at an internship program and the main problem with interns since 2023 has been their over reliance on AI tools. I feel like I have to teach them to stop using AI for everything and think through the problem so that they don't get stuck.

Meanwhile many of the seniors around me are stuck in their ways, refusing to adopt interactive debuggers to replace their printf() debug habits, let alone AI tooling...

replies(8): >>45087363 #>>45087929 #>>45088042 #>>45088074 #>>45088303 #>>45088412 #>>45088809 #>>45090665 #
VectorLock ◴[31 Aug 25 23:13 UTC] No.45087929[source]▶
Interactive debuggers and printf() are both completely valid and have separate use-cases with some overlap. If you're trying to use, or trying to get people to use, exclusively one, you've got some things to think about.
replies(1): >>45091349 #
1. jennyholzer ◴[01 Sep 25 10:18 UTC] No.45091349[source]▶
printf() users in this thread are very proud of their own ignorance
replies(1): >>45095771 #
2. marssaxman ◴[01 Sep 25 19:23 UTC] No.45095771[source]▶
I almost exclusively debug via printf / logging, and I am so stupendously ignorant that I have even written and published a multi-platform interactive debugger, to go with the compiler I also wrote (one of several, but this one was the most successful). Make of that what you will, I suppose.