Comment by applfanboysbgon
10 hours ago
Have you considered that they do trust their code review processes, and that they don't trust the generated code because it doesn't pass their process?
10 hours ago
Have you considered that they do trust their code review processes, and that they don't trust the generated code because it doesn't pass their process?
> they don't trust the generated code because it doesn't pass their process
That's not a credible scenario. Developers can either make changes by hand, or by asking an LLM, which is the common process when there is a downstream failure. Humans dont metaphorically throw their hands up and say "well the tool doesn't meet our expectations at every scale so we're not going to use it". Granted, most developers scale back how much they rely on it based on experience (good and bad).
That's very much a credible scenario. I think I use code from SO in a single digit of occasions. But I use it a lot more for giving me insight like a keyword for doing a proper web search. Or the name of a flag for a cli command, or the general shape of an algorithm or what to check in a troubleshooting session.
I won't generalize, but it's very rare for me to need code as most of my diffs are either boilerplate (generated with a tool or copied from docs or samples) or core logic that is mostly the translation of some design that I've already spent hours or days on. My core issue has always been incomplete specs from Product or incomplete docs for some tool/sdk/library (alleviated by having access to the source code).
Generated code is just not that useful, especially when designing the core architecture of a new project. And later it's not that useful either as the specs (why and how) is more valuable than any code (what).