You had to lean on that assumption that there's a massive amount being produced to make this point though.

The actual operating point is that the slop is made faster than humans can WRITE it.

Reviewing 100 lines of code thats 90% there and took 3 minutes to produce is faster than writing it from scratch, there's no getting around that.

For me the issue with it is that all (hyperbole) work is about to become reading instead of creating, dull.

Cool assumption. But pretty sure it's not how things work at all but sounds great...

What actually happens is that you have a long list of multiple maintainers reviewing , and multiple branches for testing, and multiple layers of review too.

https://www.kernel.org/doc/html/next/process/maintainers.html . See that long list of maintainers for a start.

The actual policy is that everything ends up getting reviewed by a human. If I post a patch, it doesn't go straight to master

If it's not being properly tested and maintained, it gets dropped irrespective of what it is (remember devfs?)

Also, I'm not sure about the kernel specifically, but on projects I submitted code to, they often wanted complex patches broken down if possible.