There's a bit of drama going on with the popular game manager Lutris right now, with users pointing out the developer using AI generated code via Claude.
A user asked on the official Lutris GitHub two weeks ago “is lutris slop now” and noted an increasing amount of “LLM generated commits”. To which the Lutris creator replied:
It’s only slop if you don’t know what you’re doing and/or are using low quality tools. But I have over 30 years of programming experience and use the best tool currently available. It was tremendously helpful in helping me catch up with everything I wasn’t able to do last year because of health issues / depression.
There are massive issues with AI tech, but those are caused by our current capitalist culture, not the tools themselves. In many ways, it couldn’t have been implemented in a worse way but it was AI that bought all the RAM, it was OpenAI. It was not AI that stole copyrighted content, it was Facebook. It wasn’t AI that laid off thousands of employees, it’s deluded executives who don’t understand that this tool is an augmentation, not a replacement for humans.
I’m not a big fan of having to pay a monthly sub to Anthropic, I don’t like depending on cloud services. But a few months ago (and I was pretty much at my lowest back then, barely able to do anything), I realized that this stuff was starting to do a competent job and was very valuable. And at least I’m not paying Google, Facebook, OpenAI or some company that cooperates with the US army.
Anyway, I was suspecting that this “issue” might come up so I’ve removed the Claude co-authorship from the commits a few days ago. So good luck figuring out what’s generated and what is not. Whether or not I use Claude is not going to change society, this requires changes at a deeper level, and we all know that nothing is going to improve with the current US administration.
However, for more specialized code, I would be concerned. It would likely not function at all without editing, and if it did function it probably wouldn’t be optimized or secure.
That’s not completely true. Claude and some of the Chinese coding models have gotten a lot better at creating a good first pass.
That’s also why I like tests. Just force the model to prove that it works.
Oh, you built the thing and think it’s finished? Prove it. Go run it. Did it work? No? Then go fix the bugs. Does it compile now? Cool, run the unit test platform. Got more bugs? Fix them. Now, go write more unit tests to match the bugs you found. You keep running into the same coding issue? Go write some rules for me that tell yourself not to do that shit.
I mean, I’ve been doing this programming shit for many decades, and even I’ve been caught by my overconfidence of trying to write some big project and thinking it’s just going to work the first time. No reason to think even a high-powered Claude thinking model is going to magically just write the whole thing bug-free.
You’ve described the loop I’m using to get working code. Also I ask it to look for inefficiencies like duplicated or dead code, redundant work, inefficient memory usage, and then I test again. I’m not going to catch everything wrong like this, but honestly I wouldn’t even if I were doing all of it by hand. I’m pretty happy with the results - I just updated my project’s “server” branch with a back end refactor and a CLI interface actually! Link if you’re curious: https://github.com/obelisk-complex/histv-universal
Pending some further testing I plan to roll the changes in to main.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
Welcome to the largest gaming community on Lemmy! Discussion for all kinds of games. Video games, tabletop games, card games etc.
Rules
1. Submissions have to be related to games
Video games, tabletop, or otherwise. Posts not related to games will be deleted.
This community is focused on games, of all kinds. Any news item or discussion should be related to gaming in some way.
2. No bigotry or harassment, be civil
No bigotry, hardline stance. Try not to get too heated when entering into a discussion or debate.
We are here to talk and discuss about one of our passions, not fight or be exposed to hate. Posts or responses that are hateful will be deleted to keep the atmosphere good. If repeatedly violated, not only will the comment be deleted but a ban will be handed out as well. We judge each case individually.
3. No excessive self-promotion
Try to keep it to 10% self-promotion / 90% other stuff in your post history.
This is to prevent people from posting for the sole purpose of promoting their own website or social media account.
4. Stay on-topic; no memes, funny videos, giveaways, reposts, or low-effort posts
This community is mostly for discussion and news. Remember to search for the thing you’re submitting before posting to see if it’s already been posted.
We want to keep the quality of posts high. Therefore, memes, funny videos, low-effort posts and reposts are not allowed. We prohibit giveaways because we cannot be sure that the person holding the giveaway will actually do what they promise.
5. Mark Spoilers and NSFW
Make sure to mark your stuff or it may be removed.
No one wants to be spoiled. Therefore, always mark spoilers. Similarly mark NSFW, in case anyone is browsing in a public space or at work.
6. No linking to piracy
Don’t share it here, there are other places to find it. Discussion of piracy is fine.
We don’t want us moderators or the admins of lemmy.world to get in trouble for linking to piracy. Therefore, any link to piracy will be removed. Discussion of it is of course allowed.
That’s not completely true. Claude and some of the Chinese coding models have gotten a lot better at creating a good first pass.
That’s also why I like tests. Just force the model to prove that it works.
Oh, you built the thing and think it’s finished? Prove it. Go run it. Did it work? No? Then go fix the bugs. Does it compile now? Cool, run the unit test platform. Got more bugs? Fix them. Now, go write more unit tests to match the bugs you found. You keep running into the same coding issue? Go write some rules for me that tell yourself not to do that shit.
I mean, I’ve been doing this programming shit for many decades, and even I’ve been caught by my overconfidence of trying to write some big project and thinking it’s just going to work the first time. No reason to think even a high-powered Claude thinking model is going to magically just write the whole thing bug-free.
You’ve described the loop I’m using to get working code. Also I ask it to look for inefficiencies like duplicated or dead code, redundant work, inefficient memory usage, and then I test again. I’m not going to catch everything wrong like this, but honestly I wouldn’t even if I were doing all of it by hand. I’m pretty happy with the results - I just updated my project’s “server” branch with a back end refactor and a CLI interface actually! Link if you’re curious: https://github.com/obelisk-complex/histv-universal
Pending some further testing I plan to roll the changes in to main.