Review quality says a lot about team habits

lately i’ve been noticing that code review quality says more about a team’s habits than the diff itself. some teams use reviews to catch real issues, and some just use them to prove they looked at it.

has anyone else seen that split? the odd part is that both can look “professional” from the outside until you actually live with the code for a month.