The bigger problem is that your skills are weakened a bit every time you use an assistant to write code

Not when you factor in that you are now doing code review for it and fixing all its mistakes…

It depends how you’re using it. I use it for boilerplate code, for stubbing out classes and functions where I can tell it clearly what I want, for finding inconsistencies I might have missed, to advise me on possible tools and approaches for small things, and as a supplement to the documentation when I can’t find what I’m looking for. I don’t use it for architecting new things, writing complex and specialized code, or as a replacement for documentation. I feel like I have it fairly well contained to what it does well, so I don’t waste my time on what it does badly, and it isn’t really eating away at my coding brain because I still do the tricky bits myself.

That is just dumb.

Your skills are weakened even more by copying code from someone else. Because you have the use even less of your brain to complete your task.

Yet you people don’t complain about that part at all and do it yourself all the time. For some it is even the preferred method of work.

“Using your skills less means they get weaker, who would have thought!”

With your logic, you shouldn’t use any form of help to code. Programmers should just lock themselves in a big black box until their project is finished, that will make sure their skills aren’t “weakened” by using outside help.