Juliette

@jrf_nl@phpc.social

Twitter
twitter.com/jrf_nl
GitHub
github.com/jrfnl
6Posts
0Following0Followers
Juliette@jrf_nl@phpc.social

Replying to @ramsey@phpc.social

@ramsey @elazar I'm "lucky" in that regards, poor (self-employed OSS maintainer), but at least nobody can force the use of AI on me.

I do get very very very very very very very tired of continuously having to tell people to RTFM (CONTRIBUTING guide) and to follow the "no AI allowed" rule.

Company policies will probably only change once AI companies start charging realistic prices for AI usage. The trouble they will run into then is: where can they still find skilled people to replace AI ?

Juliette@jrf_nl@phpc.social

Replying to @elazar@phpc.social

@ramsey @elazar I favour building community and upskilling people over using a completely unethical tool just because it is convenient, so, to me, forbidding any kind of AI usage is still the right choice.

Especially for software which requires a lot of contextual knowledge to create a good (correct) patch, like PHP_CodeSniffer. Even more so, knowing that PHPCS is used by AI to "keep it honest" 😄

Juliette@jrf_nl@phpc.social

Hear, hear!

I've been proclaiming this exact point as part of my "Resurrecting the Dead" talk.

Code review of GenAI PRs is no longer about training the next generation of potential maintainers, making it just a time sink, sucking the joy out of being a maintainer.

Well done AI companies.
OSS can't survive without community, so destroying the communities is a great step towards destroying open source (in favour of the AI closed garden where tokens costs 100x what they do now)....

Jan Wildeboer 😷:krulorange:@jwildeboer@social.wildeboer.net

Code reviewing was never the most interesting thing to do. But it had one important element. That, if done right, it was knowledge exchange between the reviewer and the coder. That can be quite motivating. Helping a fellow coder to become better. Reviewing "AI" written code does NOT come with that potential reward. The machine doesn't learn the way a human does. This turns code review into a menial, fruitless task that leads to frustration instead. That's my observation and opinion.

1/2