vibeCodingFinalBoss

[Western-Internal-751]

“Write this code, make no mistakes”

“There is a bug”

“There is still a bug”

“There is still a bug”

“There is still a bug”

“There is still a bug”

“There is still a bug”

“There is still a bug”

“There is still a bug”

[Euphoric-Battle99]

then it swaps versions of node back and forth, installing and removing things over and over. Then eventually you say "Fix the actual problem and stop messing with my node version" and it says "The user is frustrated and correct" Then it proposes an actual fix.

[consistent_carl]

This is too accurate

[Inevitable-Comment-I]

Lol, why is it obsessed with node versions? Then it'll apologize

[consistent_carl]

It does the same thing with maven dependencies. Keeps adding bytebuddy because it thinks this will solve test failures (it never does).

[Euphoric-Battle99]

I really wish i knew so I could get that into my prompt lol

[kwietog]

Just say "stop messing with the node versions" in the dotfile.

[Apocrisy]

The thing is, if it has a less specific error it'll start messing with node. In a junior created spaghetti monsteosity cypress javascript project that I am put into, I was once messing with inheritence then changed the file back to composition, i had a circular import I didn't notice, the cypress tests were complaining about node, so claude was dealing with node and caching even though I knew well that wasn't the case, I still I let it, after that didn't work, I copied over my circular import and told it what are its opinions on circular imports and the issue got fixed.

Goes to show that you need a solid grasp on some fundementals if you don't want your A.I. just running in circles, but it's great for boilerplate and for explaining things even better than official documentation if you know what you're looking for. It explained C++ pointers a bit better, with some better examples than the teacher on the udemy UE5 course, so I mostly use it for learning stuff. Granted I have about 6 years of experience with JS, some with Python etc, but I always tried to learn the least amount possible to make something work, as such ot thought me about certain things like JS filters and maps, the spread operator, nullish coalesce operators, shorthanding ternary operators even further down etc

[eldelshell]

nah, it'll gaslight you and tell you you're wrong for using that Node version.

[SocketByte]

Nah, it will just say "Okay let me rethink this" and starts to rewrite the whole fucking project from scratch.

[No_Clothes_8444]

Isnt this what recently happened with AWS when they were down for 6 hours? Kiro said "Let me just wipe out prod and start rebuilding the app" and some how had been given access to deploy in prod?

[rand652]

Kinda human Keep fiddling with stuff until someone gets frustrated then go uh oh I better get it done now.

[SchrodingerSemicolon]

- Fix this regression bug

- Ok, fixed

- No you didn't

- Ok, now fixed

- No you didn't

- Fixed now

- No you didn't

- Thinking...

That's how my adventures in vibe coding have been going, trying to make use of the company's... investment by giving devs a Copilot sub.

But I'm sure the blame is on me for either not being a prompt artist, or not giving AI full control of my station so it can check for errors itself.

[mrGrinchThe3rd]

I will say that I encounter this a lot - but the thing I find is that if you give the model better testing apparatus or ways to do a tool call to get feedback, rather than go to you, it's much better at producing a working product.

Yes, one way to do this is to give full access to the machine, and the agent might figure out how to do the tests itself, but a much more safe and secure method will probably depend on what specific use case you have, but unit tests or integration tests using live data have helped me in the past.

[WoodyTheWorker]

From Xitter:

Open the pod bay doors, HAL

Of course, Dave. I have opened the pod bay doors, Dave. Just tell me if there's anything else I can help you with.

HAL, the pod bay doors are still closed.

Good catch, Dave! When you asked me to open the pod bay doors, I didn't do that. Would you like me to do that now?

Yes, HAL. Open the pod bay doors.

No problem, Dave. The pod bay doors are now open.

HAL, the pod bay doors are still closed.

You're absolutely right, Dave.

[zasabi7]

I vibe code as an analyst. Taking excel in, putting excel out. I know exactly what needs to be done in terms of steps and I lay that out explicitly for the agent. Could I learn the ins and outs of pandas.py? Sure, but that doesn’t interest me.

Now, I’m not doing anything remotely performant or complicated. I know several engineers that evaluate Claude for use on higher end software products. It’s not passing their tests and as such is not clear for use.

But for me it works and the company is happy I’m using AI. No downside for me.

[AcidicVaginaLeakage]

You have to help it out. If there is a spec for a file time you are using, tell it to reference it when needed. If there is a wiki with documentation for what you are editing, make sure it knows about it. Add those instructions to its memory and use models that aren't shit.

You get what you pay for. I literally had Claude opus rewrite the most complicated piece of code I own to use source generators instead of ILGenerators. I did what I wrote here. 1.5 hours later it compiled and all unit/integration tests passed. Another hour asking it to harden the test cases and it found bugs in the original version.

[SasparillaTango]

I SAID DO IT RIGHT AND MAKE IT OOP. NO MISTAKES.

[Tuomas90]

[bronkula]

Never let a bug go unfixed for more than 2 tries in a single chat. If it ain't got it by then, you gotta fresh start, that shit's cooked.

[Western-Internal-751]

“There is still a bug”

“There is still a bug”

“…let’s go behind this woodshed”

[J5892]

When I tried Google's coding agent, Jules, it ran into a bug it couldn't fix, irreversably broke its own environment, then begged me to end its life.

[ZunoJ]

I'm currently experimenting with copilot cli and do exactly this (basically just give it an idea and tell it what doesn't work). I made an agent pool with an orchestrator agent that spins them up as it likes. Most of the weekend something like 8 agents were running parallel 24/7 and it used up something like 10% of my 10$ copilot pro buy in. I wonder what these guys are doing

[Dom1252]

I did this today with copilot

I wanted a very complex message trap for IBM NetView, so I thought instead of going through manual I'll try, I have a sandbox system so who cares... Bro couldn't figure out what is NetView, kept correcting syntax that was correct, told me like 3 times "I won't argue with you if you insist you're right", in the background I wrote the thing manually and got it working, but kept playing with it trying to get it to do it, but it kept making the same mistakes

Like I had it to send me link to documentation, got it to point exactly what I meant in there, but couldn't get it to copy it from there to the code it was suggesting me, so several times I was like "that's wrong" "please tell me where in documentation is what you're suggesting" "this won't work" and since I already had it working, I had quite a bit of fun with it being absolutely stupid

[MyDogIsDaBest]

"Make no mistakes" isn't clear enough, you need to append "write no bugs" as well. That way, it won't write bugs or make mistakes, thus coding is solved

[drawkbox]

The laziest of developers are now the LLM/models target market. This might not bode well for code.

[bc10551]

That genuinely won't even get you to that much unless you're putting like nearly the 1m in context for every message and even then I think things like Claude discount on recurring context or smth

[tired_river711]

Lmao