We faced a lot of this this year. Eager new joinees sent 100s of lines of CLs to review to "improve" little things.

Not only did the new changes did not fix what they thought it would fix but it broke other things in unexpected ways.

I brought in two changes after that:

* I'm not reviewing/reading anything that you yourself did not read / test in the target environments properly. If all it takes is an LLM prompt, I could be issuing the same prompt to make my life easier.. and If you're sending a CL, you should be owning the code you send.

* Me being more involved in the design process so review burden itself becomes lower. A bit of pair programming from time to time helped too.

Not sure how things will turn out after this but so far they seem better.