I think you're right in general. I think juniors and those who havent yet had experience are not going to understand a goddamn thing and produce broken, insecure, unmaintainable slop.

I've written my share of garbage code -- completely by hand! And i'm much better for it.

Once you have that experience, once you've written a few backends and frontends, there's not much left to understand. Move the data from here to there. Display it, transform it, slice it up. For webdev AI is a huge force multiplier. I can make a dozen features or apps in the time it used to take me to learn one framework I was curious about. It even helps me learn faster because of how quickly I can test new patterns and ideas.

There's certainly a right way to use it if you want to continue being edified, burning the planet down aside.

Fully agree.

Unfortunately many people would rather spin the wheel for a chance to win magically produced functioning code, rather than doing the work themselves with sure results - even if it takes the same or more time. And the kind of current politicians there are around the world proves that most people don't give a fuck about the ice-caps (though I would also argue that it's not so much the random person calling an LLM that is poisoning the waters - even though it does have a non-negligible effect -, rather it's massive sociopaths in charge of the companies creating LLMs that are perfectly fine with destroying the environment and other people's money in a vain dream of being the owner of some kind of "new order")

This is a point that really sticks with me. Using it for the sometimes spot on cakewalk segments is a fairly productive win. By the time you stubbornly insist on driving it entirely blackbox with chat and trying to get the right results without actually touching code... Well, even when it works, it's often more work than just doing it yourself.

Someone rebased a UI I worked on in a new version of the UI framework. As a result, there was this one odd gap in the UI in one specific place. A vibe coder spent 3 hours back and forth with the AI trying to get it to correct the gap and finally submitted their merge request. Hundreds and hundreds of lines of CSS. So I declined the merge request, open the gui, looked at the gap, hit f12, adjusted a single padding statement, and it was all good. People are struggling with defining all sorts of criteria and rigging it to let it try and try and try again and hopefully laid out every contingency, every corner case, and spent hours laying the ground work and could have done similar in a more straightforward way.