I think it comes down to team/company preference. I would really prefer a culture that allowed (at least) 2-8 hours for a larger code review of features. That

I think it comes down to team/company preference. I would really prefer a culture that allowed (at least) 2-8 hours for a larger code review of features. That way you can block time out for it and digest things. A company culture has to allow that. People get reluctant to review the large PRs because they know they have to other work to do. A bunch of small model/service/repository PRs seems tedious to me. If I want the consider the whole picture, I also have to go back to each PR.