WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2026 Poal.co

281
Don't get me wrong, working with people can be great. However, I've sensed a weird compulsory nature to what I've see happening lately. I've see literature that suggests at least part of the reason for forcing pair programming is to dispel the notion that programming is a male-only, solitary job, thereby making it more attractive to women. What do you think?

Don't get me wrong, working with people can be great. However, I've sensed a weird compulsory nature to what I've see happening lately. I've see literature that suggests at least part of the reason for forcing pair programming is to dispel the notion that programming is a male-only, solitary job, thereby making it more attractive to women. What do you think?

Yes
No
Fuck You!

(post is archived)

[–] 2 pts

This should generally only happen with noobs or if you are explaining a repository to a new employee.

I am on a team of 3 in a company of about 100. I know the code that my counterparts will produce before they send me the PR because we have been working together and reading each other's code for so long.

There is no time for two people to do one person's job. If I struggle with something I make a branch, pass it to my coworker and they see if they can fix it while I work on something else. The idea of two people opening a new branch, declaring new classes together just sounds wasteful to me.

However, I peer coded with my wife yesterday . She is learning React and I thought I could help. I hate react now.