291
u/UnreadyIce 1d ago
Today's vibe coding version is to prompt the AI just "fix it" whenever there's an error, only for it to not work again, and repeat the whole process, up to around the 10th attempt, where your free token usage for the day runs out
46
u/Firemorfox 23h ago
Do they like... not just ask the AI about the error codes, or do any unit testing, ask it to provide similar stack overflow posts, then debug manually?
Or are the new vibe coders just completely averse to debugging manually?
IDK, I just know my code is shit, the AI makes code that's shit, but since it does it faster and I have to debug either way, I don't see the difference. (this is in reference to small simple functions, and not large projects overall. in that case, it's 100% a fault of programmer's skill for not abstracting sufficiently)
20
u/No_Preparation6247 19h ago
IDK, I just know my code is shit, the AI makes code that's shit, but since it does it faster and I have to debug either way
I think you figured out why AI code is becoming more popular. It's faster even if the quality... isn't.
3
u/Firemorfox 17h ago
The quality isn't utterly horrible if you abstract sufficiently, either.
That said, I'd much rather just use Copilot. Language AI was not designed for programming in mind, it was to imitate language. I'm waiting on whatever programming-focused AI will be released by Google in the future, personally, and using Copilot until then.
135
u/metalmagician 1d ago
Imagine if you paid attention and addressed the issue described in the error message. It's a compilation error, not a runtime error
26
u/Fun-Measurement-2612 1d ago
Is he stupid?
13
u/TastySpare 1d ago
Isn't there a saying along the lines of "the definition of stupidity is doing the same thing over and over, and still expect different results"?
12
1
u/Mucksh 47m ago
Sadly had often have where recompiling the same code really fixed the issue. One time i searched 3 days for an bug only for it to vanish after a full clean rebuild. Since then it's one of the first things i check if something doesn't add up. Usually stupid easy fixable mistakes e.g. messed up the build order.
27
u/Tuckster786 1d ago
Reminds me of on my of my classes in college. A bulk of the assignments were the professor gives us a program with a bug, and we had to fix it. Usually it was stuff like variables being wrong, indents wrong, and lool logics. There was one assignment that everyone hated. The "bug" in the program was the professor added a statement saying if true throw compiler error. It wasnt actually a compiler error through it was just a console log saying compiler error
16
u/Aikenfell 1d ago
I bet the professor was laughing his ass off
He psyched y'all out so hard you missed the simple things
Then again that's just like regular programming
2
u/GoddammitDontShootMe 15h ago
Was this a language like Python where running and compiling aren't separate steps?
6
13
u/Tight-Requirement-15 1d ago
The IDE definitely would cache everything of that build
5
u/Sync1211 1d ago
*Laughs in Visual Studio*
One of my recent projects always fails the first build after a cleanup. (And it shows a ton of errors before the first build which disappear after the build fails)
The reason for this is that building assembles a DLL, but that step runs too late or something, so it isn't included when doing code generation/DLL processing.
(The errors as caused by generated code being missing which is fixed during the first build. That's a non-issue)
1
u/meighty9 3h ago
Yeah, recompile, clean solution + recompile, or restarting Visual Studio and trying again are perfectly valid things to try in the dotnet world.
6
4
5
u/EthanAlexE 22h ago
To be fair, sometimes it's visual studio's fault. There are several times I have recompiled the same code that failed and visual studio just decides that it remembers what an integer is
2
u/Awfulmasterhat 1d ago
Maybe a project clean and computer restart will... Wait it actually worked??
2
u/AuelDole 1d ago
I love in c++ getting the << or >> wrong and having a seven page long complete error in return
1
1
1
u/SysGh_st 20h ago
Clear the cache and try again. Code is sound. Compiler is wrong. It just doesn't know it.
1
1
u/GoddammitDontShootMe 15h ago
Why would anyone expect it to work if they didn't change anything?
1
u/Olorin_7 11h ago
what i was joking about here is sometimes if you fix an error or just do a change in the code it doesn't register it fully so keeps failing you just have to keep trying to compile it again and again till it catches itself
1
1
u/merotatox 7h ago
Me recompiling the same Rust code for the 100th hoping the rust compiler will get bored and let me through
1
u/Azazel_Rebirth 5h ago
Me helping a coworker troubleshoot and I don't notice they don't have autosave on.
Happens way more often than I'd like to admit
1
u/Highlight448 3h ago
How do people get so many errors, I'm genuinely curious. Do people even read the errors? Should be pretty easy to debug.
207
u/Percolator2020 1d ago
Stop throwing errors once, to psych him out, then more!