Follow
Code review is an essential part of team maintenance of #software. It must be a conversation . Pushing code without review might feel like getting things done, but it creates a form of technical debt. The other maintainers have not taken in the new logic yet, and therefore cannot act on it. That can mean duplication of work or breakage, since the other developer was not aware of the new logic.
@sergii because you need a team that is all on the same page, since they are working together on building something.
@eighthave on other hand when you wanna move fast and break things, code review is waste of time. In case tech debt is at acceptable levels, why bother with reviews?