if the only point of hiring junior devs were to skill them up so they’d be useful in the future, nobody would hire junior devs
I never said that, and a single review already will make a junior dev better off the bat
LLMs aren’t the brain: they’re exactly what they are… a fancy auto complete
I agree, but then you say...
type a function header, let if fill the body… as long as you’re descriptive enough and the function is simple enough to understand (as all well structured code should be) it usually gets it pretty right: it’s somewhat of a substitute for libraries, but not for your own structure
...which says the other thing. Implementing a function isn't for a "fancy autocomplete", it's for a brain to do. Unless all you do is reinventing the wheel, then yeah, it can generate a decent wheel for you.
let it generate unit tests: doesn’t matter if it gets it wrong because the test will fail; it’ll write a pretty solid test suite using edge cases you may have forgotten
Fuck no. If it gets the test wrong, it won't necessarily fail. It might very well pass even when it should fail, and that's something you won't know unless you review every single line it spits out. That's one of the worst areas to use an LLM.
fill lines of data based on other data structures: it can transform text quicker than you can write regex and i’ve never had it fail at this
I'm not sure what you mean by that.
let it name functions based on a description… you can’t think of the words, but an LLM has a very wide vocabulary and - whilst not knowledge - does have a pretty good handle on synonyms and summary etc
I agree with that, naming or even documenting is a good way to use an LLM. With supervision of course, but an imprecise name or documentation is not critical.