Just learned a team at Microsoft is doing code reviews *after* merge
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
Post-merge reviews make a lot of sense for new apps that aren't in prod yet.
Favor moving fast and breaking things early when the stakes are low. Then as we get close to prod, slow down enforce pre-merge reviews to avoid issues impacting prod.