Another issue with pair programming - the assumption that the benefits which are potentially produced by pairing, are often baked into estimations regarding qua

Another issue with pair programming - the assumption that the benefits which are potentially produced by pairing, are often baked into estimations regarding quality of work and / or deadlines. The current product I work on has had a team of - count em - two developers for the past year. I'm the one that is full-stack, so I get to help the less-experienced developer work on our frontend, while I have minimal time to work on the backend solo (for the most part). My pair programmer partner, also has no interest in learning the new dev-sec-ops our company is pushing - so I get to also solo all of that work. It's an extremely frustrating / soul-crushing scenario to be in. It's basically punishment for exhibiting competence and willingness. It's a situation I'm hopefully out of in the next month.