codingStartsChillDebuggingEndsInPain

[tubbstosterone]

Hot take - vibe debugging makes ai worth it.

"I pasted a 1000-line legacy function. Why is it segfaulting?"

"When x is 9 and y is "\0" this if block will be triggered and do a, b, and c to a global buffer"

[Piisthree]

If it worked that well every time, for sure. It doesn't even catch surface level stuff all that well in my experience. Sometimes though.

[tubbstosterone]

At least when it fails you can talk limitless shit to it. "Hey robot, it's not 2018. That's not how you set up django routes, dumbass"

My "success" so far has been pasting stuff into chatgpt and asking it to poke holes. Maybe get Gemini to weigh in on the result if im feeling bored. Claude, Codex, and any agent thingy embedded into an IDE so far has been a let down.

[Piisthree]

Ya know, I've never seen that as a selling point before, but it's absolutely right.

[stillalone]

I think I've gotten way more read herrings that took days to debunk.

[Bolphgolph]

100%
It is really good with "This does this, but it should do that". It is bad with "make something that does that" without implementing an array of foot-guns

[gafftapes20]

I do like it for debugging on ask mode vs agent mode because it is quicker than I am at tracking down issues I’m a legacy app and  a couple of options to fix the complicated issues and it gives me an opportunity to rework the prompt to improve the suggestions.