On Code Review
I find post-coding, pre-merge code reviews ineffective, for a change.
The code was already written. Time&#x2F;money spent. Finding out that solution is subpar at this stage is costly, and delaying integration makes ineffective teams.<p>If you want to enforce standards, automate it (there are multiple highly configurable tools for that).
If you want good solutions, pair program.
If you want to maintain good codebase, review it periodically (codebase, not some changes to it contained in pull request) and refactor. Use TDD &#x2F; BDD to ensure the app still works.