Although this article is about vibe coding, I enjoyed its conclusion, that the best coding comes from doing it with others. This is why Plone has lasted so long: it is about collaboration and learning from each other, and it is a social construct.
"learning and coding is about motivation, reward, comprehension, understanding the future, and most importantly doing all this amid other people"
This is just one aspect of the medal. Although I delivered a critical talk on AI and vibe coding a few weeks ago at the Plone conference, I had some positive experiences with vibe coding in areas where I’m not particularly skilled, such as frontend work. I managed to create a very visually appealing landing page for myself. Additionally, I’m currently working on a new website for my concert choir (which has been struggling to relaunch its 20-year-old site for years) using Hugo, incorporating a modern design. Vibe coding allows us to explore new possibilities and tackle challenges beyond our comfort zones. However, as the article emphasizes, it’s crucial to have a solid understanding of our work and a strong foundation is preferable to simply diving into something without prior knowledge.
I agree with @zopyx
Also consider that most of the skill is learning the framework, not making the project. About non-determinism, the code we write depends on the day, on an idea, on a vision that changes over time.
The question is just: how solid and reliable is the AI code? And what is coding by a machine that is coded itself? It is highly inefficient to perform 1+1 using an AI versus a CPU instruction, so we need to empower AIs to use the right tools. AIs tend to replicate best practices, so if I've to output a web page and we tell nothing, it will use some of the existing web frameworks and designs for fanciness. But this will produce a lot of code, CPU cycles, RAM consumption, and whatever, just to please the asker.