Pull requests versus pair programming

From ym2149.org
Revision as of 21:09, 20 March 2024 by Andrzej (talk | contribs) (Created page with "* I believe pull requests can be a cheaper way of achieving the same benefits as pair programming * But this requires a lot of discipline from the developer and the reviewer == Good article == * https://mtlynch.io/code-review-love/ of which i 100% agree with most points * writing a description should be a simple case of linking back to the Jira ticket * put cosmetic changes (if absolutely necessary) in their own commit so reviewers don't have to consider them * the rev...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
  • I believe pull requests can be a cheaper way of achieving the same benefits as pair programming
  • But this requires a lot of discipline from the developer and the reviewer

Good article

  • https://mtlynch.io/code-review-love/ of which i 100% agree with most points
  • writing a description should be a simple case of linking back to the Jira ticket
  • put cosmetic changes (if absolutely necessary) in their own commit so reviewers don't have to consider them
  • the reviewer may have fresh eyes, but none of the context, and should appreciate the author has made decisions based on much more knowledge of the situation
Retrieved from ‘https://ym2149.org/index.php?title=Pull_requests_versus_pair_programming&oldid=138’