Like imagine if your hobby was cooking, but you hated the cleanup. If you buy a robot that automates the fun part at the cost of making twice the mess, that is not a good trade off no matter how many extra cookies you end up with.
I'm lurking around the OpenBSD mailing list and it seems that code review is where collaboration starts. You send a patch, explain its purpose, people try it out and comment. If it's OK (various factors decide that), it's imported inside the codebase.
The main issue in corporate settings is that the author of the PR wants to browbeat you into accepting his/her changes. Either directly or by appealing to the manager. They don't want collaboration, they just see you as the blocker between them and the "Done" status on the ticket.
The workers will see the fun evaporate but now they have to clean 10x cookie trays in the same 8 hours.
We’re kind of at the fast food point: before LLMs, bring successful at all in software required some level of skill (witness all of the companies getting very expensive write-offs from off-shoring or big consultancies trying to save on payroll vs. staff), kind of like how the small cafe/bakery model needed to have at least some level of craft to have something people would buy before the option of making food at a factory and shipping it became an option.