I don't think approaching this with a sense of helplessness really helps anythingmistbow wrote:During the rapid development phase, there's no point in contributing; testing and creating issues are sufficient. It's no longer a problem to write code as before; the problem is then polishing it and making sure the software runs like clockwork. Perhaps if it's a completely new feature that wasn't planned, then it makes sense, but unless it's something unique, there's no point in creating a PR at this stage.Not enough momentum and things don't move, but if every change is "5 steps in some direction" I think that is a recipe for issues, and makes collaboration extremely difficult.
Imagine you have someone who wants to help, they look at some bit of the code and think "oh i can improve this" and next week that entire section of code is changed. Do you think they will say "oh time to review all of these changes and discard my work" or "well I'm not part of the AI junior dev team so why bother"
Would you accept a 1k line commit from someone who said it was AI generated and worked on their machine? Would you ask AI to review the code they shared? would you take the time to read every line and be sure it's good for the project?
Although there was a recent precedent in the repository https://github.com/coregx/gxpdf, where someone wrote about 10 high-quality small PRs, which I accepted after his revisions. Whether he used AI or not, I didn't question it, but his contribution was valuable. So I think there's no point clinging to the old development style; the world has already changed, and there's nothing we can do about it...


