I used to work on a team of two and we skipped code review. It was no reason really, just that we didn't see the benefits outweighing the overhead. That was pro

I used to work on a team of two and we skipped code review. It was no reason really, just that we didn't see the benefits outweighing the overhead. That was probably wrong, as a lot of bugs, conflicts, and even some documentation could have been avoided if we had code reviews. There was an earlier situation where we also skipped code review because the coders were all hotheaded cowboys who worked 5 PM to 5 AM, and this was the kind of thing that would just add tension. Also not necessarily a good idea, but we had a high enough political cost trying to implement a daily stand up.