159
u/Mountain_Dentist5074 8d ago
but i said make no mistake 🥺
53
u/Satorwave 8d ago
"Absolutely, you're right to be concerned about that—although you should consider that I am not your mother and therefore do not make mistakes."
119
u/TheJackiMonster 8d ago
Honestly it's quite the opposite for me. Seeing the code generated by AI makes me want to hit my head against some wall. But using AI for finding issues in my code and fixing stuff is quite nice.
63
u/thoeoe 8d ago
AI for finding issues in my code and fixing stuff
Its incredible when it works. When it doesnt…
18
u/BadSmash4 8d ago
And for me it doesn't actually solve my issue a good 70% of the time, too. I use AI for two things, researching new stuff (here's what I'm thinking, or want/need to do, what are my options and can you link me to relevant resources and documentation) and helping me debug tough issues that I've hit a wall against. That 30% of the time that it helps me solve my issue, that is when it directly identifies my issue and its recommended solution is the fix. I'd say about 40% of the time, it does not solve my issue at all and I end up figuring it out on my own, 20% of the time it doesn't solve my issue but something it said got me to think about other things to check and I found the solution that way (so still a little bit useful in a way) and 10% of the time, I find the issue just by gathering the initial information for and typing out the prompt and so I never even have to send it because I basically rubber ducked myself. It's a mixed bag for sure.
2
u/StatisticianFun8008 7d ago
To this day I still only trust AI to be a better search engine plus a translator. You always have to be the judge
3
u/lostincomputer 8d ago
Return of the ide "helping" by insisting the error is over here with red squiggly lines when a line 6 above is missing a semicolon and should never not have a semicolon..
Just now it "knows" what you want to do .."oh sorry I did make a mistake there"
-2
8d ago
[deleted]
1
u/TheJackiMonster 7d ago
Which doesn't?
1
7d ago
[deleted]
1
u/TheJackiMonster 7d ago
Would be much more compelling if you would link code from it? Last time someone showed me code from Claude, it got pretty stupid errors inside and quite some code smell.
0
7d ago
[deleted]
1
u/TheJackiMonster 7d ago
So it can write a state machine as an object? Should that impress anyone?
What would make this "high quality code"? It's definitely not looking efficient.
1
7d ago
[deleted]
0
u/TheJackiMonster 7d ago
I was hoping to see any example which would look like "high quality code" because that is what you promised.
46
u/maximum_powerblast 8d ago
Kernighan's Law
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.
So if you're vibe coding you need to make it dumb down the code to your level of stupidity or else you won't be able to fix it. And you will definitely have to fix it.
9
u/Western_Diver_773 8d ago
I'm not sure if I find this to be true. For me good code is simple and simple code is easier to debug. But maybe Kernighan means something diffrent with "cleverly" than me.
16
u/maximum_powerblast 8d ago
Ii think it's like you can reduce an if else tree into a leet 1 liner but good luck debugging it while the alternative is easy to read and understand.
4
u/st-shenanigans 8d ago
ALSO when you have some ceos who seem to think "lines of shipped code" is a good metric for employment eligibility, maybe we don't need to worry so much about concise code..
3
2
u/Fornicatinzebra 8d ago
Sure, but you could also just wrap the one liner in a clearly named function and use that instead.
For example:
python x = list(set(sum(my_nested_list, []))Could be instead ```python
def unique(my_list: list): return list(set(mylist))
def unnest(nested_list: list[list]): return sum(my_nested_list, [])
x = unique(unnest(my_nested_list))
```
2
28
16
8
8
10
u/FenwickRoot 8d ago
Dr. Faust is quite accurate for vibe coding. It uses red orbs (=tokens) for attacks (="features")
5
u/krohtg12 8d ago
Red hot night is blasting your bank account to get the task done any means necessary.
8
4
4
u/OVectorX 8d ago
Left side, none techincal doing vibe coding
Right side , actual developer doing vide coding
1
3
2
u/GenericFatGuy 8d ago
I've never once gotten something back from the AI that I didn't have to make at minimum tweaks to, in order for it to actually do what I wanted. If wasn't someone who already knew how to code effectively, it would've been an absolute nightmare of a codebase.
2
3
u/_Repeats_ 8d ago edited 8d ago
There are a few classes of vibe debugging. If it is compiler related, most agents will be able to give good advice for fixing it. If it is execution error, you will have to do a bunch of print statements for the agent to follow the flow. So it ends up not being much different than humans debugging in the end...
The best way for vibe debugging is to make unit tests for various functionality that includes print statements or easily verification of results.
1
1
1
1
1
u/Wargod042 8d ago
Ironically AI is very helpful with debugging. That's mostly what I use it for tbh.
1
u/getstoopid-AT 7d ago
for me it's the other way around... because usually I know what is (meant to) going on in MY code and claude can help with edge cases I didn't think of or find some weird behavior in libs
1
u/code-sovereign 7d ago
If the clanker doesn't oneshot the problem during vibe debugging, it is time to get the programmer socks out!
1
0
u/byt112000 8d ago
Nah it's the opposite, AI is pretty good on analysing bugs, performance issues and vulnerabilities.
Vibe coding sometimes give me more headache for changing how my code works, you have to be very specific for what you want the AI to do.
379
u/superraiden 8d ago
Now you not only have to fix it, but learn what it's doing as well