> That's why code review process must have a guidebook with a rule "it's on the reviewer to show why the suggested change has a tangible benefit". Agreed, yet

> That's why code review process must have a guidebook with a rule "it's on the reviewer to show why the suggested change has a tangible benefit". Agreed, yet you're implying that: - there must be a guidebook in the first place - that it must actively be followed Sadly, that is not the case in many environments, where disagreeing with another developer might actually make you waste more time discussing (or rather) arguing things back and forth, rather than just doing the changes that they want.