PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
81–90 of 162 posts
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#82The problem is really behavioural, not the tooling. People that do not understand, test and document their decision making in their PRs should not be submitting them, regardless of what tooling (AI or otherwise) they used to create them. This problem existed before AI, but it is now just worse due to the spamming nature of these "contributors". It's another form of endless September where people unfamiliar with the n…
No, it is a tooling problem. The tooling is telling laymen that they built wonderful things that definitely work and perfectly fix and add features. The tooling gasses them up and is simply wrong in these cases. If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#83The problem is really behavioural, not the tooling. People that do not understand, test and document their decision making in their PRs should not be submitting them, regardless of what tooling (AI or otherwise) they used to create them. This problem existed before AI, but it is now just worse due to the spamming nature of these "contributors". It's another form of endless September where people unfamiliar with the n…
No, it is a tooling problem. The tooling is telling laymen that they built wonderful things that definitely work and perfectly fix and add features. The tooling gasses them up and is simply wrong in these cases. If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#84I recently just started using Claude/ChatGPT/China models for some PS3 homebrew work. Every model seemingly falls flat in this scope of programming. The PS3 is very complex and the tooling is fairly undocumented in a lot of instances. It doesn't surprise me most of these AI PR's are nonsense. If anyone else has attempted writing PS3 homebrew apps using AI and has refined their tooling/systems/automation please let me…
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#85I’ve read so many stories like this that I’ve actually gotten scared of making PRs open source projects. There’s one in particular where a feature I really wanted didn’t exist, so I forked and had Codex 5.5 assist with building the feature on my local version. It works perfectly. My life has been improved in being able to have this feature now. Normally I’d want to share it back with the community so others can benef…
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#86I recently just started using Claude/ChatGPT/China models for some PS3 homebrew work. Every model seemingly falls flat in this scope of programming. The PS3 is very complex and the tooling is fairly undocumented in a lot of instances. It doesn't surprise me most of these AI PR's are nonsense. If anyone else has attempted writing PS3 homebrew apps using AI and has refined their tooling/systems/automation please let me…
Similar for me, but regarding the Classic Macintosh APIs. The difference is that there are plenty of books, and some source code available… just not enough to stop Codex from writing subtly wrong gibberish. I get the impression that the “10x velocity!!!!” claims still only reflect which areas have a sufficient corpus to learn from, rather than any inductive reasoning.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#87The problem is really behavioural, not the tooling. People that do not understand, test and document their decision making in their PRs should not be submitting them, regardless of what tooling (AI or otherwise) they used to create them. This problem existed before AI, but it is now just worse due to the spamming nature of these "contributors". It's another form of endless September where people unfamiliar with the n…
No, it is a tooling problem. The tooling is telling laymen that they built wonderful things that definitely work and perfectly fix and add features. The tooling gasses them up and is simply wrong in these cases. If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue.
Can a voltmeter _lie_ to you?
EE are expected to know when their measurements are wrong. And Professional Engineers are legally accountable for consequences of such mistakes.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#88The problem is really behavioural, not the tooling. People that do not understand, test and document their decision making in their PRs should not be submitting them, regardless of what tooling (AI or otherwise) they used to create them. This problem existed before AI, but it is now just worse due to the spamming nature of these "contributors". It's another form of endless September where people unfamiliar with the n…
No, it is a tooling problem. The tooling is telling laymen that they built wonderful things that definitely work and perfectly fix and add features. The tooling gasses them up and is simply wrong in these cases. If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue.
It's a human issue if you don't recognise that the code it's generated is wrong. That will never change no matter how good the tooling gets.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#89what is the appeal of blindly blasting open source projects with high-volume PRs? If you're trying to help the project to accomplish something, it doesn't follow that a firehose approach is tenable, if only for the fact that reviewing the code takes time.
Re: PS3 Emulator Devs Politely Ask That People Stop Flooding It with AI PRs
#90Earlier quoted context omitted.
No, it is a tooling problem. The tooling is telling laymen that they built wonderful things that definitely work and perfectly fix and add features. The tooling gasses them up and is simply wrong in these cases. If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue.
If your tool regularly lies, gaslights and produces wrong results, that's a tooling issue. It's a human issue if you don't recognise that the code it's generated is wrong. That will never change no matter how good the tooling gets.