The OP has a point. Pair programming into somebody's else code, with no context of the overall functionality, and having to use somebody's else system (diffe

The OP has a point. Pair programming into somebody's else code, with no context of the overall functionality, and having to use somebody's else system (different shortcuts, editor layout/environment), is a very poor experience. I have been in two of them, and they were not a pleasant experience overall. Most senior engineers take some time to understand what's going before diving into somebody's else code and making changes left and right. We all have that experience where fixing a bug, the right way, starts causing/surfaces other problems in the system. I am talking as a dev that has shipped multiple apps, and some of them very successful. In anyway, if it works for you, keep on doing it, but it will absolutely turn off the more experienced folks from your company.