> The author may call it "vibe coding", that's fine but it has little to do with LLMs.

Humm.

Maybe if we say that this is not an issue from vibe coding it wont be?

Maybe if we pretend that maybe a naive junior would make these mistakes (true) we should be happy to accept them from senior developers (false)?

LLMs are extraordinarily bad at doing these things.

I’ve seen it.

You've seen it.

The OP has seen it.

You’re in a rush so you wrote some classes in a code base in a language which supports classes but has no classes in it?

Really? Did that get past code review before? Did you deliberately put up a code review that you knew would be rejected and take longer to merge as a result because you were in a hurry?

Of course not.

You did the bare minimum that still met the basic quality standards expected of you.

I get it. We all get it. When youre in a rush you cut corners to move faster.

…but thats not what the OP is talking about, and its not what I see either:

Its people putting up AI slop and not caring at all what the content was.

Just a quick check it compiled and the tests pass if youre lucky.

Too lazy even put a “dont use classes” in their cursor rules file.

Come on. The OP isnt saying dont use AI.

Theyre saying care, just a little bit about your craft ffs.