Theme 1 – Loss of craftsmanship and intrinsic satisfaction
Many commenters feel that AI removes the hands‑on, challenging part of coding that gave them joy and a sense of identity.
“I personally used to enjoy the challenge of it. I enjoyed the craftmanship. I am so glad I got to enjoy the challenge of implementing IETF specs and the debugging interop etc… it's so sad to me now that people just bruteforce all this with agents.” – Sean‑Der
“Actual doing is usually responsible for the long‑term satisfaction people derive from work. Cut that out and you're just managing an email inbox.” – grebc
“Whatever feeling of craftsmanship and skill I had is gone, now it's mostly mechanical.” – slopinthebag
Theme 2 – Overwhelm from low‑quality AI‑generated contributions
Maintainers describe being flooded with poorly considered PRs that force them into triage work rather than creative development.
“I am getting outlandish PRs against Pion. So I spend my time triaging and feel burned out. The ‘AI future’ I was expecting would be people swooping in and clearing up the backlog in high quality ways. Instead I get people trying to add new APIs when it can already be done with existing APIs and then arguing about it with me.” – Sean‑Der
“How do you filter without putting up barriers that high quality contributors will not want to climb?” – voakbasda
“Make it a rule that any PR that changes over … 100 LoC? 150?
needs to be broken down into smaller, more atomic ones.” – cassianoleal
Theme 3 – Coping strategies: setting boundaries and using AI selectively
Several participants advocate protecting their time, insisting on quality thresholds, or leveraging AI for tasks that augment rather than replace their craft.
“You are well within your rights to require submitters reach a certain standard before you will review your request… You are allowed to be ruthlessly protective of your time to the benefit of your project.” – suprjami
“After a while, I found two things that have helped: 1. Leaning into other areas where AI can boost my skills rather than just replace them… 2. Taking on more ambitious projects.” – dcastm
“I only maintain my own codebases… I’d imagine I’d just want to turn repo’s private or gate who has access, that’s my default response.” – grebc