The point is that cooking was never criminalised in my analogy, only cooking with mushrooms. I also already wrote why that might be preferable to making the ban on poisonous ingredients

“Claude please read this post and come up with a clever response for me”

The company I work at has fully embraced vibe coding, so from my experience: it did seem faster at first, but also the amount of regressions and new bugs being introduced has gone up dramatically, and so the overall workflow has stabilised to be roughly just as fast as before AI, but now almost all mental energy is going into QA and reviewing. From the customer perspective, they saw lots of new progress initially, but have now been frustrated by constantly finding things broken or buggy.

And all this is at a company which has entire teams dedicated to trying to improve AI-based workflows and tools to make them more reliable.

So no. From someone in the field, quality has dropped a lot, and speed is only increased if you close your eyes and ignore all the tech-debt being created.

It’s more like banning cooking anything with mushrooms in it, because we haven’t sorted out which mushrooms are poisonous or not. You could make it more accurate by instead banning cooking with anything poisonous, but of course then lots of people will keep cooking with their mushrooms, naively thinking they are not poisonous and therefore allowed.