I like it a lot for tasks, that are a bit more tricky. Banging out API design prototypes with a second pair of eyes is quite productive because you have a potential 'consumer' with you. After a while you can switch, change perspective and repeat the process. Debugging with a partner tends to be quite helpful as well. You are forced to 'externalize' your thoughts (speaking out loud to explain what you are doing) which often helps (me at least) to not trip over logical errors.
For common routine tasks I wouldn't use pair programming. Everything, that is routine doesn't really benefits from a second person. Super creative work (e.g. working on a really weird algorithm or other hacky thing) might also not be the best target as I usually don't have the capacity to vocalize my thoughts in this context. The results from this kind of work could (and maybe even should) be a good reason to get a colleague and evolve on the design.
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.
I like it a lot for tasks, that are a bit more tricky. Banging out API design prototypes with a second pair of eyes is quite productive because you have a potential 'consumer' with you. After a while you can switch, change perspective and repeat the process. Debugging with a partner tends to be quite helpful as well. You are forced to 'externalize' your thoughts (speaking out loud to explain what you are doing) which often helps (me at least) to not trip over logical errors.
For common routine tasks I wouldn't use pair programming. Everything, that is routine doesn't really benefits from a second person. Super creative work (e.g. working on a really weird algorithm or other hacky thing) might also not be the best target as I usually don't have the capacity to vocalize my thoughts in this context. The results from this kind of work could (and maybe even should) be a good reason to get a colleague and evolve on the design.