This perspective on vibe coding is both funny and contradictory. The core issue with vibe coding is that people ship things they don’t understand. To flip it around and blame it on the humans involved only after something goes wrong as if the issue is them vibe-coding “wrong” is foolish. The issue is the vibe coding.

I'm too old to keep up with the hip jargon these days; isn't "vibe coding" different from just using a coding agent?

"Why blame vibe coding?"

Because it allows you to produce so much code that it's not viable to carefully review each line/module, and get the benefits of the fast output.

Writing code yourself forces your brain to start creating pathways in your brain and you can verify the correctness of those pathways in your mind (e.g. am I actually doing this right, if I have seen such API would I be happy to use it,...)

Not saying we should write code manually, just showing the differences.

Because "skill" is too generic to be a useful categorization of reality, so people identify more specific causes

Was going to say the same. In fact we're seeing a huge wave of hacks caused by old human coded systems getting owned by "vibe" attackers.

Vibe coding is such an overused term now. Stats say what, 80% of programmers use AI to generate code? 90%? So everything is vibe coded. If you do well, no, it's still engineering. Someone makes a mistake? Cuts a corner somewhere? Vibe coded.

There probably was no human in the loop.

Or more possibly the person incompetent one.

Vibecoding amplifies human mediocrity and enables grift.

how many forced "tokenmaxxing" initatives do I need to bring up before we stop blaming developers for this reckless adoption of AI? These decisions come from the top, often from people who do not understand the software.