on small PRs

  • If a task is big enough, multiple small & focused PR’s are a solid way to approach it
  • A PR with 2 lines changed is ok
  • If your environment allows for it, follow ship/show/ask
  • Mitigates risk by having feedback earlier in the dev process
  • Helps keep reviews focused, and high quality
  • Easier rollbacks and identification of issues
  • Works well when combined with markdown notes next to the code

Works well when combined with Microsoft’s zero defects methodology

zero defects meant that at any given time, the highest priority is to eliminate bugs before writing any new code

  • With that said, each small PR should leave the pipelines green, with hopefully no breaking changes