this post was submitted on 23 Jun 2023
40 points (100.0% liked)

Programming

17677 readers
38 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

I've been working in programming for a few years and I think I really dislike Pair Programming; I understand how it is but I often find it mind-numbingly dull. I have a feeling I'm doing it wrong but I feel like as a part of a dev team tasks should be broken into discrete enough chunks that a single person can just blitz through the work... Maybe it's just me, what are y'all thoughts on the matter?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 25 points 2 years ago* (last edited 2 years ago) (1 children)

No you're not weird, pair programming is not one size fits all solution.

EDIT: To be clear, I still find value in pair programming, but a mandatory pair programming, for me is quite absurd. It should be organically happening, for example, a junior asking for help from senior.

[โ€“] [email protected] 9 points 2 years ago* (last edited 2 years ago)

I have found it quite effective while pair programming (senior to junior mentorship) to say OUT LOUD exactly what I'm changing and why I'm changing that. This allows others to more easily follow your train of thought and can lead to good discussions rather than turning PRs into essays.

However, as other comments have mentioned, this can get exhausting.