It is exactly the opposite, with simple, predictable auto-complete you didn’t have to worry about that anymore, with LLMs you always have to look at it in detail because every little thing could be just plain completely different and wrong.
I can read way faster than I can type though. You still check it, but it’s pretty good as that kind of stuff once you have an example for it to follow.
Reading code is usually orders of magnitude slower than writing code. Sure, typing might be slower than reading but to check if it is what you intended you have to understand it too.
Well, I’m generally very anti-LLM but as a library author in Java it has been very helpful to create lots of similar overloads/methods for different types and filling in the corresponding documentation comments. I’ve already done all the thinking and I just need to check that the overload makes the right call or does the same thing that the other ones do – in that particular case, it’s faster. But if I myself don’t know yet how I’m going to do something, I would never trust an AI to tell me.
Well, okay, I can see how it would be useful in languages like Java that are extremely verbose and have a low expressiveness. Writing Java pretty much was already IDEs with code generation 20 years or so ago because nobody wants to write so much boilerplate by hand.
Those are the easy time savings though, the safe easy stuff the developer doesn’t have to worry about anymore. (Giving them time do the gnarly stuff)
It is exactly the opposite, with simple, predictable auto-complete you didn’t have to worry about that anymore, with LLMs you always have to look at it in detail because every little thing could be just plain completely different and wrong.
I can read way faster than I can type though. You still check it, but it’s pretty good as that kind of stuff once you have an example for it to follow.
Reading code is usually orders of magnitude slower than writing code. Sure, typing might be slower than reading but to check if it is what you intended you have to understand it too.
Well, I’m generally very anti-LLM but as a library author in Java it has been very helpful to create lots of similar overloads/methods for different types and filling in the corresponding documentation comments. I’ve already done all the thinking and I just need to check that the overload makes the right call or does the same thing that the other ones do – in that particular case, it’s faster. But if I myself don’t know yet how I’m going to do something, I would never trust an AI to tell me.
Well, okay, I can see how it would be useful in languages like Java that are extremely verbose and have a low expressiveness. Writing Java pretty much was already IDEs with code generation 20 years or so ago because nobody wants to write so much boilerplate by hand.