No idea if "mob programming" is effective or efficient, I'd like to see some proper experiments on that, but what you described in the first few paragraphs is not a code review. A review is a process, not just sending code to a colleague. No wonder things went wrong. A proper code review is egoless. Rigorous reviews, such as formal inspections (recommend Software Inspections by Gilb and Graham) have a tremendous payoff.