
Skipping Reviews and Post-Merge Reviews

Code Reviews, AI, and Modern Engineering 🔍 — with Greg Foster
Topic 5 of 9
Published Jul 11, 2024 · Clip 21:02–27:40 (6:38)
Greg shares the example of Watershed, which did post-merge reviews for velocity but eventually rolled back to standard pre-merge reviews as they scaled. He says deviations from code review are acceptable case-by-case for low-risk changes like docs or internal tools, if you accept the security and context tradeoffs. He argues the real fix for feeling blocked is stacking, not skipping reviews.