2026-06-30 14:55 UTC
@godotengine@mastodon.gamedev.place LOUDER !
AI contributions have the added pain of being demoralizing. Reviewing PRs is already tedious work, but it is rewarding because reviewers generally feel that their efforts are contributing to educating a new contributor (who may become a future maintainer/reviewer). If your feedback on PRs is just being absorbed by a machine and not going towards mentoring a potential future maintainer, it becomes much harder to justify spending your free time on PR review.
Replies (3)
-
@alex@social.alexhyett.com 2026-07-01 09:16
@orange_lux@eldritch.cafe @godotengine@mastodon.gamedev.place this 100%!
-
@SReyCoyrehourcq@social.sciences.re 2026-07-01 13:20
@orange_lux@eldritch.cafe @godotengine@mastodon.gamedev.place poke @zimoun@social.sciences.re Linked to PRs review that becoming pain in the ass with llm...
-
@tschundler@leds.social 2026-07-02 03:34
@orange_lux@eldritch.cafe I feel strongly that way about code review at work. I didn't mind needing to make corrections because it was mentorship. I'm connecting with a colleague and we are both growing. But reviewing some vibe coded garbage, are they learning? They're mostly just having the LLM do the fixes too. It feels more empty and more draining. I'm not so enthusiastic about being just a debugger and a gatekeeper. @godotengine@mastodon.gamedev.place