There's a limit to amount of code review before hitting decision fatigue.
Welcome new world. *nap time*
Discussion
Big PRs might need extra friction then, like if your PR exceeds 20 files or 5000 changes, a label needs to be added or something or approval is needed.
That will incentivize smaller PRs.
Or just have other incentives like measuring time to merge and setting a goal.
It’s all about the incentives.
one thing i really wish junior devs would do better, is cut down on the number of unnecessary changes and off target features. Its very easy to get distracted and not stay on target, cuz its cheap to add garbage code
smaller, higher quality code, with better architecture is what we should be striving for.
tiny well architected code bases. yep. incentives do matter as well. indeed.
Afternoons doing code review at my day job are the worst, I've almost dozed off at my desk before 😓
Smaller PRs make code review easier.
Either way, CR is essential. AI can't do it nearly as well