Pre-merge code reviews are often dismissed as harmful to team culture, but in dysfunctional teams lacking tests and refactoring skills, they can actually reduce blame culture. By following five simple rules — opening PRs early, never merging your own code, never merging code you don't understand, reviewing before starting new tasks, and contributing commits over comments — responsibility for bugs shifts from individuals to the team collectively. This collective accountability encourages teams to invest in automated tests, mentorship, and shared tooling. The broader lesson is that best practices always carry context, and what works for high-performing teams may not be the right starting point for struggling ones.
1 Impression