OP here, you're welcone! I'm thrilled at how many awesome responses there are here. You bring up some really important questions that I think get at the heart

OP here, you're welcone! I'm thrilled at how many awesome responses there are here. You bring up some really important questions that I think get at the heart of the problems teams often have with code review. Even if it is valued in an abstract way, it isn't really treated like a first class coding task. It's not measured and planned in the same way that writing code is. It seems like a lot of comments here talk about ways to quantify code review and bring it onto more of an equal footing with writing. On my team we all informally budget time for reviewing PRs, but we don't really plan and track it with any rigor. I don't think any of us have a very good idea how much time anyone else spends on code review, which can make picking a reviewer awkward. I'm curious to hear other people's responses to your questions.