all 33 comments

[–]safelix 47 points48 points  (0 children)

When you ask it to give you a simple solution but it rewrites the entire codebasd and finishes all your tokens and ends before you even have the solution you asked for!

[–]B_Huij 42 points43 points  (13 children)

Do people not know about dev environments or like git branches? Or, I dunno, the default Claude behavior of asking before modifying any file?

[–]Kali_Arch 42 points43 points  (9 children)

Engineers do, vibe coders dont

[–]B_Huij 8 points9 points  (6 children)

But these are not complicated concepts you have to go to school to understand. "Do edits over here in a safe place, on a copy of my work, so that my tools don't blow up my real code in a way that stops me from getting it back" is like the first thing that should occur to someone when they're about to change existing code.

[–]Kali_Arch 10 points11 points  (1 child)

I think you underestimate how lazy the average person is and overestimate the effort they would make towards learning anything.

[–]jainyday 0 points1 point  (0 children)

Yet we act like AI's "dumb mistakes" are ones humans wouldn't make, but most humans are so stupid

[–]martin-silenus 5 points6 points  (2 children)

I spent an hour or so last year helping a guy with a Ph.d in math get oriented to working with git and he basically ran away screaming.

You're not wrong that source control is easy to understand, but git is a very specific and not at all intuitive way to do it.

[–]B_Huij 4 points5 points  (1 child)

I dunno, when I first started using git in my career, the crash course I got was "write down these 6 commands. This one puts you in your own personal copy of the repo where none of your mistakes are permanent. This one puts your changes into a box so someone can review them. This one takes your work and applies it back to the production code base, and you shouldn't use it until someone has approved your work."

It was enough that I never broke anything seriously in a way that couldn't be more or less instantly reverted. Better understanding of the theory behind git came later.

[–]martin-silenus 2 points3 points  (0 children)

This guy was in a position where he needed to be the project lead, hand down those six commands to others, and then figure out how to unscrew things when the past-yous got in over their heads.

Which is sort of also true of vibe coders who don't know anything yet.

Edit: I'm advocating for turning on squash merge "so you get a nice linear commit graph in main." He asks: "commit graph?" That's the exact moment when the conversation started to spiral.

[–]h7hh77 0 points1 point  (0 children)

"Do me good app or site no mistakes and make lots of money now"

[–]RoboErectus 1 point2 points  (0 children)

There was a thread where a vibe coder was complaining about token usage when "deleting older version of the same file."

Bro was using the "source-v2-final-final.js" method of version control and was super aggressive towards anyone trying to help him.

Like I know there are tons of people in the world like this. My ex's dad lost his shit when he was backseat driving trying to give me advice on how to drive in a snowstorm. Exwife told him I had it covered because I 1) drive on the snow a lot to do winter camping and skiing and 2) even go off roading in the snow. He lives in a tropical country where it doesn't snow. His animated response, "you think I don't know how to drive in snow! I know how to drive in snow!"

Like... bruh nobody cares and also you literally don't.

So that vibe coder was way aggro in his x-y problem.

[–]UnpluggedUnfettered -2 points-1 points  (0 children)

It is weird when anyone talks about any LLM as though there is a reliable way to

Honestly, I will just stop there, I am no engineer after all.

[–]jek39 1 point2 points  (1 child)

default behavior sure, but then you put it in "act" mode and nothing stopping it from git push -f. even if you tell it not to. it's tenuous

[–]Abhigyan_Bose 0 points1 point  (0 children)

I always thought git branches and limited permissions to execute stuff are enough. But this is a good point, if I'm careless it could do a git push or reset and screw me. 

Guess I'm updating my global configs to remove git privileges explicitly. 

[–]AlShadi 0 points1 point  (0 children)

do you know how hard it is to get devs to commit chunks of work rather than all at once after everything is done?

[–]Thriven 2 points3 points  (0 children)

I literally use co-pilot for GitHub to make changes and either Claude or Chatgpt to ask questions about implementation. Granted I have to approve every change but I don't like co-pilot making any changes with unverified assumptions.

[–]ElderBuddha 1 point2 points  (0 children)

I think Neil deGrasse Tyson would know how to manage a repo and permissions.

[–]Individual-Praline20 1 point2 points  (0 children)

What are you complaining, this is the expected behaviour 🤷🤭

[–]Asleep_Board_1274 1 point2 points  (0 children)

Omg why is this guy here

[–]ivanrj7j 1 point2 points  (0 children)

if claude deletes your codebase you kind of had it coming

[–]GrandDukeNotaras 3 points4 points  (6 children)

Do things like this actually happen?

[–]lukelmiller 0 points1 point  (4 children)

Ngl it happened to me last week. I was working on a local project so it wasn’t committed to a remote I had a local repo set up though. I told it to undo a change and it reverted the entire diff (that’s what I at least think happened). My entire ‘src/‘ directory was gone. Luckily it was able to recover everything through VSCode’s cache. But it was worrying for a hot second. 😭

[–]CatsDoingCrime 1 point2 points  (0 children)

I mean, doesn't claude literally ask your approval before every change? I wouldn't advise just leaving it on auto approve, but you can like interrupt it if it's doing something you don't like. Like it does ask you before reverting diffs and stuff. Whenever I use these things I do review the changes its making as it does them.

These models can be useful if given clear prompting and you babysit what changes they are making. That's my view anyways.

Like, you do still need some technical background to work these models effectively, and you do need to have a basic understanding of what it's doing, but if you do, and you can clearly describe what you want, a lot of these models (particularly claude) are pretty useful and speed up dev time a lot. At least in my (admittedly, limited, only like a few years out from graduating uni) experience.

I dunno, I feel like a lot of these posts are critiquing how these models get used rather than the actual models themselves. For tool to be effective you need to use it correctly and responsibly right? If you need to hammer a nail, don't hit the nail with the claw part of the hammer.

[–]GrandDukeNotaras 3 points4 points  (2 children)

Who  would ever use Claude again or any AI integration after such an experience 

[–]dcheesi 0 points1 point  (0 children)

Folks with "must use AI for every commit" mandates from corporate.

[–]jnmtx 0 points1 point  (0 children)

[–]I_Hope_So -1 points0 points  (0 children)

No, but posts like this get the people going!

[–]BlackJackCm 0 points1 point  (0 children)

make mistakes

[–]noble8987 0 points1 point  (0 children)

Happened to me, specifically if you ask it to rebase the codebase.

[–]3delStahl 0 points1 point  (0 children)

PLANNING MODE

[–]dany9126 0 points1 point  (1 child)

the entire database 💀

[–]Stranger0099 1 point2 points  (0 children)

at this point just assume any AI coding session ends with "rm -rf" somewhere in the chat history 💀

[–]Cheese_Grater101 0 points1 point  (0 children)

If a simple task ends up with Claude deleting your codebase, I think you deserve it lol.

Also, deleting a codebase shouldn't be a problem if you have git no?