100%, couldn't agree more - those are great descriptions of the circumstances under which pair programming is useful. We practice pair programming all the time. In fact we have an entire team optional "code together" morning that helps with 1 & 2. Our principal developer or I commit to being at Code Together's and it really helps keep the architecture simple and sane. The rest of the time, we encourage pair programming for very similar reasons to the ones you list.
I think your Low Certainty/3 is very important - unblocking challenges especially at the start create momentum, and that can last throughout an entire feature.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
100%, couldn't agree more - those are great descriptions of the circumstances under which pair programming is useful. We practice pair programming all the time. In fact we have an entire team optional "code together" morning that helps with 1 & 2. Our principal developer or I commit to being at Code Together's and it really helps keep the architecture simple and sane. The rest of the time, we encourage pair programming for very similar reasons to the ones you list.
I think your Low Certainty/3 is very important - unblocking challenges especially at the start create momentum, and that can last throughout an entire feature.