As always, Simon knows what he is talking about and neatly describes the whole situation.

However, it's not the "coding" part of "vibe coding" that is the (semantic) problem, it's the "vibe" part.

Replacing "coding" with engineering, but keeping the "vibe" part, still conveys the meaning of not really knowing what you do, but now in an even larger surface area.

It's a lot more boring, but I'm fine with "AI-assisted software engineering" as the other-end-of-the-spectrum name opposite of "vibe coding".