You’ve been given electricity and you prefer to use hand tools. Yes I get that there is a niche, but to complain about rough edges when cutting down trees cos the chainsaw was too fast, will depend om what you’re making.
If you’re in a plane or a car, then yes sure. But still, I’d rather my electricity and wrap tests around it and tell it not to use emojis and refine its output then be stuck writing boiler and no autocomplete…
You’ll find your complaining niche on the internet but the truth is everybody else that is using it just shuts up and gets on with producing value rather than being pedantic on code that will work and probably be read twice maybe 10times max again. Sure it might not be optimized, but who is optimizing first go? What a waste of time.
Code that isn’t proper (which is obviously not limited to vibe code, but I would say that nearly all vibe code is improper) is technical debt. Unless your code is going to never be used and updated (which means, you don’t actually need it and you shouldn’t waste effort producing it), it will start rotting over time, causing long term issues and making everything that it touches worse.
To a lesser extent, this is what happened with web technologies, where everyone has been doing shit because they didn’t care, and now the whole ecosystem surrounding web technologies is a horrible festering mess of putrid code.
Vibe coding does the same, but amplified extremely as it does not go through the filter of a human (yeah sure, I hear all the vibe coders screaming “but I check and fix my code” and anyone knows it’s bullshit).
In your example, it would be like plugging your house on an electricity cable, that comes from a power plant managed by monkeys pressing buttons randomly. Even if you argue that the monkeys are trained to press the right buttons, you have absolutely no control over what happens.
And let’s not forget your initial argument that vibe coding produces results faster, which is highly debated, and absolutely doesn’t hold if you want a certain quality of code (as this article shows).
So do you want electricity that takes one month to install but is safe, or electricity that gets installed in two weeks by monkeys, but burns your house down ?
It does not make sense to prioritise speed over quality when it comes to technical tools, that’s all, there is no way around it.
Truth is everybody isn’t doing archery.
You’ve been given electricity and you prefer to use hand tools. Yes I get that there is a niche, but to complain about rough edges when cutting down trees cos the chainsaw was too fast, will depend om what you’re making.
If you’re in a plane or a car, then yes sure. But still, I’d rather my electricity and wrap tests around it and tell it not to use emojis and refine its output then be stuck writing boiler and no autocomplete…
You’ll find your complaining niche on the internet but the truth is everybody else that is using it just shuts up and gets on with producing value rather than being pedantic on code that will work and probably be read twice maybe 10times max again. Sure it might not be optimized, but who is optimizing first go? What a waste of time.
It’s not a matter of optimization.
Code that isn’t proper (which is obviously not limited to vibe code, but I would say that nearly all vibe code is improper) is technical debt. Unless your code is going to never be used and updated (which means, you don’t actually need it and you shouldn’t waste effort producing it), it will start rotting over time, causing long term issues and making everything that it touches worse.
To a lesser extent, this is what happened with web technologies, where everyone has been doing shit because they didn’t care, and now the whole ecosystem surrounding web technologies is a horrible festering mess of putrid code. Vibe coding does the same, but amplified extremely as it does not go through the filter of a human (yeah sure, I hear all the vibe coders screaming “but I check and fix my code” and anyone knows it’s bullshit).
In your example, it would be like plugging your house on an electricity cable, that comes from a power plant managed by monkeys pressing buttons randomly. Even if you argue that the monkeys are trained to press the right buttons, you have absolutely no control over what happens.
And let’s not forget your initial argument that vibe coding produces results faster, which is highly debated, and absolutely doesn’t hold if you want a certain quality of code (as this article shows).
So do you want electricity that takes one month to install but is safe, or electricity that gets installed in two weeks by monkeys, but burns your house down ?
It does not make sense to prioritise speed over quality when it comes to technical tools, that’s all, there is no way around it.