Yeah, I strongly disagree with this too. I've spent a lot of time reviewing code and doing code audits for security (far more than the average engineer) and re

Yeah, I strongly disagree with this too. I've spent a lot of time reviewing code and doing code audits for security (far more than the average engineer) and reading code still takes longer than writing it, particularly when it is dense and you cannot actually trust the comments and variable names to be true. AI is completely untrustable in that sense. The English and code have no particular reason to align so you really need to read the code itself. These models may also use unfamiliar idioms where you don't know the edge cases where you either have to fight the model to do it a different way, or go investigate the idiom and think through the edge cases if you really want to understand it. I think most people just don't read the code these models produce at all and just click accept and then just see if tests pass or just look at the output manually. I am still trying to give it a go, and sometimes it really does make things easier on simpler tasks and I am blown away, and it has been getting better, but I feel like I need to set myself a hard timeout with these tools where if they haven't done basically what I wanted quickly, I should just start from scratch since the task is beyond them and I'll spend more time on the back and forth. They are useful for giving me the motivation to do things that I'm avoiding because they're too boring though because after fighting with them for 20 minutes I'm ready to go write the code.