Code reviews are a necessary evil for many teams, for which an alternative is probably needed.
Just learned a team at Microsoft is doing code reviews *after* merge.
Why? To move faster.
No more pausing work to wait for code reviews.
No need for stacked PRs.
No more time-consuming merge conflicts caused by long code review delays.
This has risks, but may work well for a team that is:
- mature
- high trust
- has strong automated quality checks