If I have to debug or maintain something, I have to understand it enough to make changes and test them. This was traditionally accomplished by having me write the code against a spec of some kind drawn up or described by those familiar with the problem space.

If I'm not going to be writing code, there will be a time hit trying to understand what came from the vibe code. Teams are going to have to learn whether it takes longer to create the code or to understand the result and whether one of these makes a useful and robust and maintainable product. And "understanding" better include looking for malicious bits of code.

TBH, I'm not personally going to be doing this cuz I'm an old fart. But there's a large number of HN readers betting their careers on this stuff. Or, probably, being forced to bet their careers.

Thought I'd add... There is a pride-of-work involved in many people's work. Take this away, make them a cog, and they might wander off on ya.

I find it strange that many people think there’s no technical reasons to oppose vibe coding. Every opposition to it is quickly denounced with strawman and ad hominem arguments.