How to deal with conflict and uncertainty about quality of requests in Code reviews?

I think what would work here is to have smaller prs which means less peer review comments but for places where that might not be feasible the first thing is to do is to have detailed pr review descriptions and second for people who are prone to changing their minds establish a quick sync before starting implementing their feedback.

That way you can learn from them but not have to worry about them changing minds later on.

Depends on the size of the change and how disruptive it is to flip flop.

In general, no, this doesn't happen in Big Tech -- by the time you get to the coding stage, there should already be rough agreement on what to code.

If the decision changes, do a quick retrospective (either on your own or with the code reviewer) about why the decision changed. What new information did you get, and what could have been done to get that info earlier?

Sharing the masterclass which also covers code review: https://www.jointaro.com/lesson/iYpRj8XfyzCSaTYnce3y/how-to-write-better-code-faster-as-a-software-engineer-11192022/