StopVibeCoding

true of stablecoins. look up do kwon

america and europe are not too far

It's not just ycombinator, it's everywhere on the internet. Too many bootlickers big government & big tech bootlickers not sounding alarms as soon as privacy violations happened is what caused this.

"The Party seeks power entirely for its own sake. We are not interested in the good of others; we are interested solely in power, pure power. What pure power means you will understand presently. We are different from the oligarchies of the past in that we know what we are doing. All the others, even those who resembled ourselves, were cowards and hypocrites. The German Nazis and the Russian Communists came very close to us in their methods, but they never had the courage to recognize their own motives. They pretended, perhaps they even believed, that they had seized power unwillingly and for a limited time, and that just around the corner there lay a paradise where human beings would be free and equal. We are not like that. We know that no one ever seizes power with the intention of relinquishing it. Power is not a means; it is an end. One does not establish a dictatorship in order to safeguard a revolution; one makes the revolution in order to establish the dictatorship. The object of persecution is persecution. The object of torture is torture. The object of power is power. Now you begin to understand me." -1984

I hope this is sarcasm. Surely, right?

it's not just their direct cost, it's also the loss of revenue. the author wasn't arguing that they could save 435 million dollars in server costs.

Instead they were arguing that in addition to saving maybe a million or two in server costs, they would gain an additional 435 million dollars in revenue because less people would leave their website

for a company the size of kroger, $435M is an extremely conservative loss. If someone did proper research and determined that it's 3x, maybe 4x that much I would belive them.

too few developers understand this

this is a good approach that I have admittedly not thought of.

At that point however, is it really saving you that much time over good snippets and quick macros in your editor?

For me writing the code is the easiest part of my job, I can write fast, and I have my vim configured in such a way where it makes writing code even faster.

When they fail they will pretend that the CEO of a messaging company is actually a criminal mastermind, and will throw him in jail for almost a week as soon as he steps into a european country, then he will not be allowed to leave the country for over a year, but I'm obviously exaggerating this would never happen, right?

[1] https://www.businessinsider.com/telegram-pavel-durov-travel-...

My comment, which, upon reflection was poorly written, was supposed to imply "remember how the European Union pretended to care about privacy, and created GDPR? That same european union wants to do this"

Remember GDPR?

copy paste from a different comment in this thread:

> I have tried being specific, I have even gone as far as to feed its prompt with a full requirement document for a feature (1000+ words), and it did not seem to make any significant difference.

No. It is different, when working with a codebase written by humans there is always sanity. Even when looking at terrible codebases, there is some realm of reason, that once you understand can make navigating the code easy.

I believe you missed the part of my comment saying that I have been coding professionally for 20 years. I have seen horrible codebases, and I'm telling you I'd rather see the switch statement with 2000 cases (real story), many of which were 100s of lines long, with C macros used religiously (same codebase). At a bare minimum, once you get over the humps, with human written code, you will always find some realm of reason. A human thought to do this, they had some realm of logic. I couldn't find that with AI, I just found cargo cult programming + shoving things where they make no sense.

This is what I heard from many people online.

I have tried beign specific, I have even gone as far as to feed its prompt with a full requirement document for a feature (1000+ words), and it did not seem to make any significant difference.

> Did you share this experience with management and your peers? What was their response?

Among my peers, there seemed to be a correlation between programming experience and agreement with my personal experience. I showed a particular colleague a part of the code and he genuinely asked me which one of the new hires wrote this.

As for management, well, let's just say that it's going to be an uphill battle :)

> What steps could realistically reverse the momentum of vibe coding?

For me and my team it's simple, we just won't be using those tools, and will keep being very strict with new hires to do the same.

For the software industry as a whole, I don't know. I think it's at least partially a lost cause. Just as the discussions about performance, and in general caring about our craft are.

it makes me feel like an absolute beginner, and not in a good way. It was such a terrible experience that I don't believe I will try this again for at least a year. If this is what programming will become in the future, then feel free to call me a luddite, because I will only write hand crafted code.

I have tested this. I have been coding for close to 20 years, in anything from web to embedded.

I got tired of hearing about vibe coding day in and day out, so I gave in, and I tried everything under the sun.

For the first few days, I started to see the hype. I was much faster at coding, I thought, I can just type this small prompt to the LLM and it will do what I wanted, much faster than I could have. It worked! I didn't bother looking at the code throughly, I was more vigilant the first day, and then less so. The code looks fine, so just click "accept".

At first I was amazed by how fast I was going, truly, but then I realized that I didn't know my own code. I didn't know what's happening when and why. I could churn lots of code quickly, but after the first prompt, the code was worth less than toilet paper.

I became unable to understand what I was doing, and as I read through the code very little of it made any sense to me, sure the individual lines were readable, functions made some semblance of sense, but there was no logic.

Code was just splattered throughout without any sense of where to put anything, global state was used religiously, and slowly it became impossible for me to understand my code. If there was a bug I didn't know where to look, I had to approach this as I would when joining a new company, except that in all my years, even looking through the worst human code I have ever seen, it was not as bad as the AI code.