Code review is about getting a team on the same page more broadly. The question posed in the article -- whether the change should be part of the product -- is certainly part of that. It's important to have a shared understanding on a team re what the code actually does and should do. But you can also use code review to align on architecture, best practices, road map.
I also find that code review helps a team feel like a team. It's nice to know anyone actually cares enough to pay attention to what you do, and feedback is an amazing gift that's really underrated.
Code review is about getting a team on the same page more broadly. The question posed in the article -- whether the change should be part of the product -- is certainly part of that. It's important to have a shared understanding on a team re what the code actually does and should do. But you can also use code review to align on architecture, best practices, road map.
I also find that code review helps a team feel like a team. It's nice to know anyone actually cares enough to pay attention to what you do, and feedback is an amazing gift that's really underrated.