What Code Reviews Really Measure — And Why Your Best Engineers Hate Them

Riya opened her laptop to a wall of red badges: seventeen pull requests waiting for her review. She was the staff engineer everyone trusted with “the important stuff,” which meant every risky change, every migration, every cross‑team integration had her name on it. Somewhere under that pile was the design doc she actually wanted to work on. She sighed and clicked the first PR anyway. It was a 900‑line diff. The description said only: “Fix stuff, please review.” Riya skimmed. The change touched a payment flow she’d helped design two years ago. There were branching conditionals stacked on top of already‑messy logic, a couple of “just in case” flags, and a new helper with a name that meant nothing. She knew what this really needed: to be split into three smaller changes, with a conversation about the underlying assumptions. That would take a few hours. The dashboard on the TV outside, though, only cared that “Time to First Review” stayed low. “Okay,” she muttered. “Nits it is.” Two commen