I don't think the article says that requiring code reviews is never good process. Consider this last paragraph: > It's up to you and your colleagues to set the

I don't think the article says that requiring code reviews is never good process. Consider this last paragraph: > It's up to you and your colleagues to set the rules for your team. Don't adopt best practices in a dogmatic fashion. Rather, ask yourself if the circumstances of others apply to you. There is a high chance that they won't, and you find a more suited way to do things. As OP scales his org he may find that the trust based approach no longer works and mandatory code reviews become the better approach. At that point it would make sense to introduce them.