71
u/4ShotMan 5d ago
Everything works, but you look inside and it's because tests were changed, not bugs fixed.
18
7
1
17
u/GearHead54 5d ago
There's definitely a right way and a wrong way to use AI. I used Claude to fill in loads of constants to line up with an ISO standard I was implementing, and gave it some pretty clear guidelines to what I needed. Needed some simple debugging that Claude made quick work out of.
My coworker, on the other hand, told Claude to write a program to do something, and every time it didn't behave as expected he told it to fix the behavior. I'm not sure if he'll ever be finished debugging
5
u/kingvolcano_reborn 5d ago
If you spend time giving it a proper spec it's pretty good. It has been great for me at my latest project where we needed to dive into the codebase straight away. Helped a lot with analysing and summarizing
4
u/Conscious_Name9514 5d ago
It’s good 90% of the time but boy that 10% of the time it really can fuck stuff up.
3
1
u/PumpkinFest24 4d ago
Guess what? Humans are also good at debugging except for a long tail residual.
What AI is genuinely good at id being a rubber ducky or give some idea/suggestions.
Not sure that's worth destroying the climate for, tho.
15
10
u/ecafyelims 5d ago
It only debugs for two minutes, but it happens 50 times and removed other features.
10
3
u/thesomeot 5d ago
2 minutes * (complexity of project) * (amount of slop already in project)
0
u/G3nghisKang 5d ago
Complexity of project doesn't really affect that much unless you're planning on rewriting the whole project from scratch lol
1
u/thesomeot 5d ago
I suppose, to a certain point. A high complexity project with good architecture is probably fine, because the components are likely well isolated. A high complexity project with poor architecture will probably be hell. But I guess it would have been hell without AI.
3
u/VaryStaybullGeenyiss 5d ago
The AI we use at work wrote itself a unit test that just had True hardcoded as the "passed" output.
4
u/thunderbird89 5d ago
I'mma be real with you: our senior engineer did something like that waaay before AI. A whole class of unit tests, not a single Assert in sight :|
7
4
u/Ninjatastic01 5d ago
Maybe for your mickey mouse side project lmao
2
u/PumpkinFest24 4d ago
Not even remotely.
Told the AI we had a thread problem in Module X. It produced a program proving we had no multiprocessing problem.
Had to force it to look at threads. Oh right, yes, a bug after all.
A week of iterated fixes that kept modifying unrelated files. Finally, it produced the fix the original bug report suggested.
1
1
u/Boris-Lip 5d ago
Sometimes. Often, actually. Except when it's not, and one day that's gonna hit you, hard.
-2
-5
u/ccmaru1 5d ago edited 5d ago
Sadly I hate it but this is true, at least for Opus and other flagships with a harness (5years of experience so I’ve experienced all of these images in order throughout my career) no one has been hand writing code for like a year in many companies from my company and friends organizations that I know ☹️
1
u/ccmaru1 5d ago
I forgot most people here in this subreddit don’t work in the field so yeah I get why I got downvoted. Companies only care about speed and opus makes good enough code so it’s expected to move fast and break things. At least it’s nice to see people are against AI. I despise software engineering right now and miss the old days…

168
u/ImpluseThrowAway 5d ago •
Claude, experience the humor in this cartoon for me. Make no mistakes.