[I'm at RealScout.] Our pairs rotate, and they work across different stories in the same epic. So more than two people (on our four person team) see the code that's being committed.
At this point, how does this not count as "code reviews"? You may not be using a PR based workflow, but it sure sounds like code reviews are in fact happening beyond simply "pair programming".
Not only is the blog title a little inaccurate, it's also clickbait.
Comments
[I'm at RealScout.] Our pairs rotate, and they work across different stories in the same epic. So more than two people (on our four person team) see the code that's being committed.
At this point, how does this not count as "code reviews"? You may not be using a PR based workflow, but it sure sounds like code reviews are in fact happening beyond simply "pair programming".
Not only is the blog title a little inaccurate, it's also clickbait.
Code reviews, traditionally, are a much more formal affair.
"Rotating pairs" means that you frequently change one half of the pair on a story or epic, to ensure constant diffusion of context about a codebase.
So for example:
Day 1: A & B work on a story.
Day 2: A rotates off. B & C work on the story and complete it. They pick up another story from the same track.
Day 3: B rotates off. C & A work on the new story.
At each point, you preserve and then share context.