This is toxic behavior that unfortunately rewards a selfish writer. I'm worried the AI push incentivizes this too much, to where in corporate situations a reader can't say no to doing work for a selfish writer.
The problem is that this is increasingly seen as a non-productive workflow slowing everyone else down, so the pressure is growing for writers to just shove massive PRs out the door and reviewers to use LLMs to make that tractable. I suppose those advocates have more faith in LLM output compared to humans than I do.
Some of this is the funny situation where the faithful will state: "This writes better code than I do!" and miss the irony of: "yes, yes it does"
"Blessed are the humble ..."
I guess it depends on what you consider "better". I've tried using LLMs to write code over the past couple of weeks with extremely mixed results.
The LLM certainly writes more interesting code! They like their cute ASCII/unicode animations, don't they?
It definitely writes a lot more code, none of it actually correct but some of it functionally similar to correct code.
If you like lots of code then I guess that's better. I like less code.
To be fair, there are plenty of situations where throwaway code is perfectly fine and/or defect risks are low enough to make the trade-off worth it. I don't think a lot of developers are thinking about it in that context, though.
(No unit tests aren't enough)
One of the few global Cluade directives I have setup is to never use emojis - and it never has, either in chat output or in code. Don't blame the tool when you don't spend 30 seconds configuring it. It's even easier with AI since you don't have to go digging for some obscure .vimrc snippet - it's literally just plain English.
Then when I get home, it's just a case of typing it in, which is the bit I'd love to automate away.
My experience with LLMs has been a bit like rubberducking code with someone who's *really* fast at looking stuff up on StackOverflow.
Even in these move-fast envs, it should be reasonably apparent for people to realize that the author should be using the LLM to make the PR tractable, not solely using the LLM to shovel out a giant PR + slop PR description.
And the LLMs can often do this - if you ask to restructure or break up a big change differently, they can often make quite reasonable suggestions and help with it. That's just not what you're gonna get if you're lazy. If you want a small LLM-generated change, often you have to start with a big one then ask it to figure out what it can get rid of, since many times it doesn't have perfect model of all the code in it's "head" before it starts spitting stuff out. The big companies have been doing their best to automate this for the last couple of years vs the even-more-blind attempts you used to get, but there's still the issue of the models+tools following generic advice aimed at median codebases vs being intimately familiar with this codebase.
You can go fast without being lazy. And when going fast, in some ways, it's more important than ever to put in that effort to not blowing things up.
Because I don't trust myself to review a giant PR. It takes too much cognition to properly review it.
And now that people are making PRs with AI, this is even more important. If the AI was good enough to have coded it, please instruct it to make the changes in reviewable chunks.
Then suddenly LLMs happened and it's like the mask is off: no one's reading them still, but also no one is writing them either.
Which is perhaps a drop in the ocean of the insanity which is "we need you to work on the Jira tasks" as basically a job title.
They've still put more effort into writing their crackpottery than you will put into reading it, and at worst it's entertaining. The late Ivor Catt's articles on "the death of electric current" - where he expounds the idea that current and indeed electric charge does not exist, because of stuff involving Maxwell's equations where the maths looks about right to me but I'm not a good enough mathematician to prove - were pretty damn odd, but his writing in 1989 on how it would be vital for an interconnected network of computers for information sharing to treat censorship as damage and route around it and some ideas for doing this was bang on the money (as we now see) and his writings on how American business management methods result in the worst possible outcome for everyone that's not already a billionaire have also proven oddly prophetic.
So maybe there's something in the crackpots after all.
How about this crackpot view? Perl vs. Python, which I guess has been replaced by Rust vs. Go - I prefer Python and Go to Perl and Rust, simply because I know them better. If you want me to work in Rust or Perl I don't really care, they're just languages. I'm not as proficient in them, expect it to take longer. Rewrite it all in Rust? Sure. I'd prefer not to, but if that's today's project then shut up and pay my invoice.
Let's see, what other things are wild crackpot ideas around here?
I don't think LLMs are very good.
I don't think self-driving cars solve the right problem.
Permaculture would be better for long-term ecological sustainability and food security than "everyone should be vegan".
Bikes would work perfectly well in American cities if you used enough of them.
So at a minimum, you could maybe fish some useful work out. PRs should be the same.
I'm not a big fan of his generally, but I highly recommend this book in particular. A lot of what he wrote there really resonated for me.
There is an implicit social contract with writing that the writer has put more effort into writing than the reader will need to read something. Sure you get crackpots still, but there are only so many Gene Rays in this world, so the volume is limited.
I think the same applies to PRs. Pre-AI , it was usually obvious when a PR was either completely terrible or very half-baked, and the required effort to create even a shitty PR was usually more than that required to reject it.
AI makes it trivial to make a completely terrible PR, and much easier to make a not-immediately-obviously-bad PR.