←back to thread

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

(www.fastly.com)
214 points Brajeshwar | 4 comments | 31 Aug 25 14:55 UTC | HN request time: 0s | 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. unconed ◴[01 Sep 25 00:22 UTC] No.45088303[source]▶
The old fogeys don't rely on printf because they can't use a debugger, but because a debugger stops the entire program and requires you to go step by step.

Printf gives you an entire trace or log you can glance at, giving you a bird's eye view of entire processes.

replies(1): >>45088752 #
2. oblio ◴[01 Sep 25 01:58 UTC] No.45088752[source]▶
Most decent debuggers have condițional breakpoints.
replies(2): >>45089702 #>>45090588 #
3. scarface_74 ◴[01 Sep 25 05:22 UTC] No.45089702[source]▶
And have since the mid 1990s at least…
4. jcparkyn ◴[01 Sep 25 08:01 UTC] No.45090588[source]▶
Not to mention tracepoints (logging breakpoints), which are functionally the same as printf but don't require compiling/restarting.