I think the point here is that it can be useful for someone who isn't really a coder, to produce just about usable simple things. But if you are a coder it's not really faster. Maybe in the short term, but in the long term it's worse.
As somebody who's been coding for 40 years, in multiple languages, I already have my own libraries full of the vast majority of stuff. These libraries are not just fully tested already, I understand them thoroughly and so can write the small changes to them needed for each project. I only need to test the changes, not the main body of code. If I use LLMs for it, I need to test every single bit of it every single time, and because I'm not learning the algorithm myself I make myself dependent on the LLM going forward. Even on those occasions where I don't already have something similar in a library it's better to write it and understand it myself rather than rely on an LLM, just in case I need something similar again in the future. And if I do the code I've saved will be fully tested in advance.
So in summary an LLM can be useful if you don't code often, and can speed up work in the short term. But using it will prevent you becoming fully experienced and will mean that you are always slower than someone like me no matter how many years' experience you get, because using it prevents you from gaining that experience. And it will always be useless for larger, more systems level projects because it is too unreliable and if you don't have my level of experience you won't be able to spot the thousands of subtle bugs it would put in such a project.
Not that most systems level projects aren't already full of these subtle bugs, but that's a whole different problem caused by Companies not wanting to pay people like me what I'm worth.