←back to thread

AI’s coding evolution hinges on collaboration and trust

(spectrum.ieee.org)
183 points WolfOliver | 2 comments | 29 Aug 25 15:24 UTC | HN request time: 0.465s | source
Show context
mikewarot ◴[29 Aug 25 16:26 UTC] No.45066139[source]▶
There's been a strong theme recently here on HN of confusing programming (the act of writing code to meet specifications) and Engineering(the writing of specifications, and the oversight of said process, along with overview of testing).

AI is definitely not ready for an Engineering role. My recent experience with ChatGPT5(Preview) via Visual Studio Code tells me that it might perform acceptably as a junior programmer. However, because I'm an old retired self taught programmer who only ever managed 1 other programmer, I lack the experience to know what's acceptable as a Junior Programmer at FAANG and elsewhere.

replies(5): >>45066216 #>>45066368 #>>45066394 #>>45066468 #>>45091373 #
1. xenotux ◴[29 Aug 25 16:43 UTC] No.45066368[source]▶
> There's been a strong theme recently here on HN of confusing programming (the act of writing code to meet specifications) and Engineering(the writing of specifications, and the oversight of said process, along with overview of testing).

You're making a distinction that might be interesting in some esoteric sense, but that doesn't exist in the industry. When it comes to software, the architects are also the construction crew. There's nothing to confuse if the terms are effectively synonymous.

replies(1): >>45067826 #
2. tjr ◴[29 Aug 25 18:39 UTC] No.45067826[source]▶
You're making a distinction that might be interesting in some esoteric sense, but that doesn't exist in the industry.

Sure it exists. Not everywhere, not for all software, but it does exist.