OP is mentioning their side of the story for what they did. I feel people are going overboard with their emotions. Few points As OP says, team members could as

OP is mentioning their side of the story for what they did. I feel people are going overboard with their emotions. Few points As OP says, team members could ask for review if they do not have confidence in what they are changing. But code reviews usually makes everyone wiser - domain context, design thinking etc., So we need to find other channels to ensure that. Few Questions: 1. Do we have data on how many bugs do we fix at review stage? 2. How many times we blindly approve based on our "trust" with our colleagues? Biases definitely play a major role in reviews. 3. What happens if one engineer quits with others not having any context? So we cannot say Code Review is not needed for every team. It may work for some. 4. How many PRs we merge using our admin rights without getting any peer review (because of delays or getting attention from our peers)?