In my project there has been this guy who produced more lines of code than most other. All of his code is terribly convoluted mess no one can work with. Also buggy and slow as hell. It’s been many years since he left the company, and the negative effects are still seen today.
Luckily we’ve been able to detach ourselves from the worst parts.
Flamekebab@piefed.social 4 days ago
Is this why so many of these fuckheads are keen on LLMs? They’re great at vomiting out reams of code.
AA5B@lemmy.world 4 days ago
My biggest objection is unit tests. LLMs can actually be a useful tool for populating out unit tests. But of you let them run amuck, you get vast quantities of tests that add no value but now you have to maintain in perpetuity
This one junior developer didn’t notice the ai brought in a whole new mocking tool for a few tests and didn’t understand my objection.
Flamekebab@piefed.social 4 days ago
I had a dev add a load of unit tests that mocked values and then tested for the mocked values. I mean… They passed…
CeeBee_Eh@lemmy.world 3 days ago
My experience with this is the LLM commenting out the existing logic and just returning true, or putting in a skeleton unit test with a comment that says “we’ll populate the code for this unit test later”.
Tangent5280@lemmy.world 2 days ago
It’s so ridiculous, like an ancient Egyptian slave telling its master that “we will” “take care of it later”
So stupid for an LLM to do
black0ut@pawb.social 3 days ago
Relying on a chance machine to thoroughly test your code sounds like a recipe for disaster
aesthelete@lemmy.world 4 days ago
With emojis in it for extra flair!