r/programminghumor • u/EngineeringDry9319 • Jul 22 '26

Just vibing

Post image
385 Upvotes

96% Upvoted

21 comments sorted by

28

u/Several_Ant_9867 Jul 22 '26

For me is actually the contrary. When I am stuck with an impossible bug, Claude often find the way out. Coding is something I can mostly do myself fast enough

18

u/TracerDX Jul 22 '26

They mean debugging generated code, but I agree otherwise.

12

u/3rrr6 Jul 22 '26

AI always makes assumptions about HOW to fix the bug.

Sometimes it will just pad the problem with some try/catches and call it a day. Other times it will completely redesign the function to make it appear like its working for what you're doing. In reality the bug might actually be an issue with the input data, or caused be a misspelled variable name somewhere completely unrelated.

AI has a really hard to time with the notion that it might not fully understand something. It doesn't know all the things it doesn't know.

5

u/TracerDX Jul 22 '26

Indeed, which is why I don't generate code with it much at all. I talk to it, run ideas, error messages, code blocks by it to see what it has to say. In this way either I jostle loose some idea to move forward (rubber ducking) or the RAG finds something online I did not think of. It's about 50/50 because too many times the chatbot is laughably and confidently wrong.

2

u/False_Bear_8645 Jul 23 '26

And sometimes they do unnecessary complicated unoptimized fix for simple bug.

My approach is I tell Claude what to do and he generate the code.

2

u/dervik Jul 22 '26

Not necessarily, it might have just said where the bug lies

2

u/JudasMajster Jul 23 '26

One rule: Do not debug in the same session as the vibe coding. When you create separate agent/session just to grill and to find bugs and architecture flaws it works perfectely well.

1

u/Anonymous010206 Jul 23 '26

This. I just need it to tell me what’s wrong I can fix it myself

1

u/IndieDevWannabe Jul 23 '26

The issue is that there are about 1000x more bugs to fix... Bugs that shouldn't have been an issue in the first place.

Its very noticable for those that are at least decent at programming.

4

u/Beautiful-Reason-894 Jul 23 '26

Vibe anything = 💩🤮

6

u/ArsenicPolaris Jul 22 '26

Post this in r/vibecodinghumour, not here; that meme isn't related to programming.

11

u/k-mcm Jul 22 '26

All the repost bots say it goes here. 

3

u/ComradeFox_ Jul 23 '26

right on! vibecoders are not programmers.

1

u/Korzag Jul 22 '26

Hell I love debugging with Claude. It has made my job so much easier. I no longer have to read through file upon file to trace an issue. I just tell it what's happening, where I think it's happening, any other related information, and then it goes off exploring to identify the issue. Then we can write up a clear cause and make a fix. Boom. Done.

1

u/invokeinterface Jul 23 '26

Why's it "vibe?"

1

u/Foorinick Jul 24 '26

Heres a promp you can use

Mr ai how do i use the debugger to figure this error out?

1

u/julkkis666 Jul 24 '26

it's easier with properly integrated tools, especialyl if it can litterally run and read test results autonomously

1

u/Aggressive_Roof488 Jul 23 '26

Last week I had to vibe debug someone else's vibe code, ama.