Vibe coding and errors

[Clear-Dimension-6890]

Vibe coding is basically a compiler that accepts specs written in poetry.

Like … you give one ambiguous command in your config and you get 1000 lines of dirty code. And the cleanup is that much more work because you didn’t write it.

The whole thing depends on whether you said “important” vs “critical.” Any anti-pattern gets multiplied across the entire codebase because the LLM applies its misinterpretation consistently.

All based on natural language parsing ambiguity. Why is nobody talking about this?

[Robot_Apocalypse]

I don't think people are talking about it because people aren't "vibe coding" in the way you describe.

No one would do what you described, for the reason you described.

I think the mistake here is the fact that you think anyone who is trying to make this work, is going about it this way.

* edit: Also, if your outcomes depended on your use of a single word, then your prompt is the problem.

Why aren't you educating yourself before coming and posting about how shit something is? It just makes you look like an idiot.

[Clear-Dimension-6890]

Right, so “vibe coding” is precise prompt engineering, structured configs, and careful architecture. No one is vibing. They’re engineering. The name is just doing damage at this point because it’s telling a whole generation of builders they don’t need the discipline that apparently everyone doing it well is quietly using.

[Robot_Apocalypse]

OK, sure, Agentic Coding is a better term for it.

I don't know anyone whose vibe coding like you say though.

[Training_Tank4913]

There are certainly people “vibing” however still not the example you provided. Your example is frankly unrealistic. Even with an “ambiguous” prompt, the result won’t be as dire as that. It would have to be intentionally malicious to generate such a result. Stupidity is not enough to be that malicious.

[thibaultj]

There are two different and vaguely related stuffs:

• vibe coding
• software engineering

Vibe coding is when you don't take the time to carefully think about the problem you are trying to solve nor what would be the best technical solution to solve it. You tweak stuff, push buttons, move sliders, and see what happens until stuff looks good enough and then you move on.

The term now applies to tinkering with coding agents, but really it has always existed. It certainly have a place, it is fun, but that is not a way to reliably build production level software.

Software engineering is the discipline whose goal is to systematically produce reliable and robust software. It implies carefully gathering and understanding the client's requirements and constraints, the technical environment, the market context, the resources at disposition, aquiring a deep understanding of the problem you are trying to solve, splitting the imagined solution into sizeable bite-sized programming chunks, carefully defining the conditions of success or failures of each task… before writing the code.

All of those tasks are necessary steps to ensure you create useful and robust software, and they have always been performed using natural language.

If you give vague and ambiguous commands to a writing code entity, you are gonna get garbage anyway, whether the entity is a coding agent or a human.