[grumpymouse]

It’s probably the same deal as with LLMs generating code: it can crank out something that’s probably broken, and the person using the LLM needs to be able to know how to code to see where it’s broken. Companies might be able to reduce the headcount of programmers / copywriters / artists but certainly not replace them right now (or possibly ever).

[ptdn]

I suspect that a coordination between a human programmer and an LLM doesn't require strong programming skills, but it does require strong debugging fundamentals. A month ago I had ChatGPT write a function in Racket just given a text description. Take two lists of symbols of any arbitrary length (but only if both lists are the same size) and construct a new list which selects one at random from the other two lists at the same location. There was some other logic in there, too, based on the way I'd done the structs.

ChatGPT wrote the function perfectly on the first shot, but then I realized it was only working most of the time -- turned out ChatGPT had done a really obvious off-by-one error in the loop, and it was breaking on (1/n) attempts where n is the size of the list.

It's exactly the same as how ChatGPT usually knows what formulas and approaches to take when solving graduate-level mathematics, and its reasoning about the problem is pretty good, but it can't get the right answer because it can't add integers reliably.

[gtirloni]

> strong debugging fundamentals

Something that experienced (and expensive) programmers are good at, incidentally.

[ptdn]

Yes, of course. The only people with good debugging skills are the people who have spent a lot of time debugging their own code (or the code of others). However, in an LLM-dominated environment, it may be plausible for someone to develop strong debugging skills while having only mediocre programming skills. This would be similar to the "boot camp web developer" archetype who has reasonable skills only in a narrow domain.

Full transparency: I think I'm one of those bad programmers who is a good debugger, but I've also been a full-time Linux nerd since Ubuntu 8.04, so I'm very comfortable reading error messages.

[alfalfasprout]

Even if the code isn't broken the issue is that the vast majority of code isn't written in a vacuum. Refactoring, rearchitecting, etc. is quite tricky.

And writing code is the easy part. Architecting is where things get tricky and there are a lot of subjective decisions to be made. That's where soft skills become really important.

[sirsinsalot]

> it can crank out something that's probably broken, and the person using the LLM needs to be able to know how to code to see where it's broken.

Same with my junior devs

[maaanu]

I see this claim so often and I fail to understand it every time... What kind of junior devs do you hire, where this is the case? And what kind of tasks do you give them?

[sirsinsalot]

It was a cheap shot at junior devs, not a serious statement