←back to thread

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

(www.fastly.com)
214 points Brajeshwar | 1 comments | 31 Aug 25 14:55 UTC | HN request time: 0.331s | 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 #
1. jacquesm ◴[01 Sep 25 02:09 UTC] No.45088809[source]▶
The right tool for the right job. If someone gets the job done with printf() then that would be good enough for me.

Interactive debuggers are a great way to waste a ton of time and get absolutely nowhere. They do have their uses but those are not all that common. The biggest usecase for me for GDB has been to inspect stacktraces, having a good mental model of the software you are working on is usually enough to tell you exactly what went wrong if you know where it went wrong.

Lots of people spend way too much time debugging code instead of thinking about it before writing.

Oh, and testing >> debugging.