←back to thread

214 points Brajeshwar | 1 comments | | HN request time: 0s | source
Show context
lpapez ◴[] 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 #
Gigachad ◴[] No.45088074[source]
I've tried the interactive debuggers but I'm yet to find a situation where they worked better than just printing. I use an interactive console to test what stuff does, but inline in the app I've never had anything that printing wasn't the straightforward fast solution.
replies(2): >>45088154 #>>45088847 #
gdubs ◴[] No.45088847[source]
I'm not above the old print here or there but the value of an interactive debugger is being able to step and inspect the state of variables at all the different call sites, for instance.
replies(1): >>45091372 #
1. jennyholzer ◴[] No.45091372{3}[source]
it's genuinely embarassing that the printf() diehards in this thread are not clear on this detail.