This is our new bottleneck too. Developers roles are shifting to spec writers and code reviewers more and more. I don't think I'd call this wasted effort though (unless the code produced is worse than what developers would have produced otherwise). I'd think of it as a good problem to have.
We're doing several things to alleviate this, and I'm genuinely curious how other teams are handling this too.
- We have Claude running code reviews on our PRs too 😄. In our department, a PR isn't expected to be reviewed by a dev until the author has addressed or reviewed and dismissed all of the issues Claude has brought up.
- There is pressure for developers on our team to become better reviewers. I think this is good, because reviewing code is a more valuable skill to prospective employers than writing it is anyway.
Is this why my Logitech mouse is so sluggish at times across different applications on OpenSUSE Tumbleweed?