Here's my opinion on those points, if people care.

• Indeed, that's why I'd love for local models to be enough for my needs. Not yet the case but hopefully someday
• It's already half my week. Explaining in natural language, to my coworkers, what they need to do. Either directly or through tickets
• I don't think it's always the case. IDE already have powerful tools but they don't come close to the "understanding" an LLM can have on your code.
• The generated code is reviewed exactly like any other of my coworkers code. I check it does what it says on the tin and passes tests.
• All code ends up like other people's code. You don't always remember what something does a few months from now. Overall we read more code than we write, so the importance of the code being readable and easy to understand is the same as before. You're still the one getting woke up a 4am, not the LLM.
• Not really true. I can implement a feature once and have it implemented and extended on all other services. The LLM mostly understand there are differences between them and work around that. Is it perfect? Ofc no, but I've never seen an automated tool you can just point at a file and say "do the same for x and y".
• Programming still needs to be done by humans most of the time. LLM are just parrots so they cannot create some new API that a human previously had to create. I like making architectural decisions, organizing the code and structure it how I want. I don't like having to edit 25 files to make some small adjustments. In the same way a "Refactor" button did not make us stop programming, LLM won't either.