Comment on Fed up with vibe coders, dev sneaks data-nuking prompt injection into their code
Sibshops@lemmy.myserv.one 3 weeks agoIn this case the prompt was just to delete usage of his package in the third party project.
Comment on Fed up with vibe coders, dev sneaks data-nuking prompt injection into their code
Sibshops@lemmy.myserv.one 3 weeks agoIn this case the prompt was just to delete usage of his package in the third party project.
kibblebits@quokk.au 3 weeks ago
Doesn’t matter. Malicious commands to delete. Uncool. Could just have easily have put a command to refuse to use it based on licensing. But nooooo. I hope they get blackballed and leave software.
Sibshops@lemmy.myserv.one 3 weeks ago
There’s zero chance an open-source developer volunteering to write and maintain software will get blackballed.
okwhateverdude@lemmy.world 3 weeks ago
Vet your deps. The whinging going on about actually doing the damn job is depressing. Git gud, you poser.
kibblebits@quokk.au 3 weeks ago
Lmfao. You’re a joke. You don’t go line by line and everyone knows it.
okwhateverdude@lemmy.world 3 weeks ago
Yes, I do read every single line and I expect my direct reports to read every single damn line, too. When I find shit in their MRs they missed, it is pointed out and it is expected they fix it. I won’t merge slop. And yes, we use clankers to generate a lot of code. When you’re responsible for systems involving millions of euros and regulatory scrutiny, there is simply no other choice. My highly valued skill set in grokking large code bases very quickly and developing cogent changes was honed over decades of experience. It is people like you that have ruined our profession by regressing to the mediocre mean.