One could argue that this does not apply to larger organisations. However, that opens up many questions regarding work culture, productivity, overhead and, ultimately, ethics.
Tnx for the comment. Discussing tools (in this case, vibe coding) naturally raises the issue of what skills are actually needed to use them effectively, such as prompting, which in turn leads to a broader question about the role and relevance of traditional software engineering skills. It's a whole other topic...
You can create value with vibe coding. As I said, know your trade-off, your context.
You wouldn't use a hammer to fix a watch, would you?
Just picture this convo somewhere in nature, at night, by a fire.