←back to thread

Some things to expect in 2025

(lwn.net)
258 points signa11 | 1 comments | 16 Jan 25 22:55 UTC | HN request time: 0.215s | source
Show context
kirubakaran ◴[17 Jan 25 00:45 UTC] No.42732804[source]▶
> A major project will discover that it has merged a lot of AI-generated code

My friend works at a well-known tech company in San Francisco. He was reviewing his junior team member's pull request. When asked what a chunk of code did, the team member matter-of-factly replied "I don't know, chatgpt wrote that"

replies(16): >>42733064 #>>42733126 #>>42733357 #>>42733510 #>>42733737 #>>42733790 #>>42734461 #>>42734543 #>>42735030 #>>42735130 #>>42735456 #>>42735525 #>>42735773 #>>42736703 #>>42736792 #>>42737483 #
Taylor_OD ◴[17 Jan 25 02:15 UTC] No.42733357[source]▶
This is more of an early career engineer thing than a ChatGPT thing. 'I don't know, I found it on stackoverflow' could have easily been the answer for the last ten years.
replies(4): >>42733857 #>>42735217 #>>42735441 #>>42738914 #
devsda ◴[17 Jan 25 03:42 UTC] No.42733857[source]▶
The main problem is not the source of solution but not making an effort to understand the code they have put in.

The "I don't know" might as well be "I don't care".

replies(1): >>42735007 #
1. arkh ◴[17 Jan 25 07:39 UTC] No.42735007[source]▶
That's where you'd like your solution engine to be able to tell you how to get the solution it is giving you. Something good answers on Stack Overflow will do: links to the relevant documentation, steps you can go through to get a better diagnostic of your problem etc.

Get the fire lit with the explanation of where to get wood and how to light it in your condition so next time you don't need to consult you solution engine.