Maybe not every single thing, but you should know what your lines of code that implement it do. You can't debug if you don't know why you wrote what you wrote.

>This is essentially how I started programming as well way back in time. I didn't know exactly what the Perl code I copy-pasted did, but if it solved the problem, it solved the problem. It brought me and my family out of poverty, and at that point, I couldn't care less about how the magic actually was done, just that it did work.

Ok. Great that it pulled you out of poverty. That's irrelevant to your argument, but Im glad for you. I guarantee you that the code sucked regardless. You might not care that you produced software that sucked, but it still guaranteed sucked. If you copy and paste code without knowing what it does, you are a bad programmer. Someone, somewhere, is going to have to clean up your mess. And they are cursing your name right now.

Unironically, I can and do. I took classes in college for things like ASM and logic gates. That's not the point I was making, though. The point is that you need to know how to read your code so that you can fix it if you have to maintain it. Or, if ChatGPT is down(like today) or not giving you the right answer, you can still do your work, albeit a little more slowly. My worry is that people will just plop whatever into a compiler, and leave buggy code that introduces bugs and security vulnerabilities. An LLM is only as good as its data source, and with things like ChatGPT and Github copilot, that data source is programmers both experienced and inexperienced. Use it, love it, but don't rely on it. Implement best practices, and use your head.