DEV Community

Discussion on: Pair programming...or not?

Collapse
 
raddikx profile image
Morillas

Due to my personality, pair programming drains my energy. The longer I'm in pair programming mode the bigger the break I'll need once it's done. I've been in few minutes pp, a whole day or even several days in a row. However I still like it and I see many advantages like:

  • Mentoring, when one is more senior than the other.
  • Live code review since, in the end, you are designing and coding with another person.
  • Share knowledge. Two people are designing and developing the same task.
  • Self improvement. You can always learn something from your colleague and improve yourself.
  • Team building. During pair programming you have the opportunity to get to know better your colleague and that always changes the relationship with her/him.

However, as I said, I like doing it but no regularly.

To your questions:

  • I pair sometimes. It depends on the project and the task and their needs.
  • I don't always pair with the same person. My answers above also applies to this answer.
  • I don't choose it. The needs of the project choose it for me usually :)
  • Luckily I never paired with a lazy or a smartass person.
  • Not necessarily. I see it like two people working together on a same task, more than one coding and the other reading over the shoulder. What it's awkward for me is that there are people who are more anxious of being the owners of the keyboard and you notice it. In that case I don't have a problem in offering them the keyboard.
  • At this point you can guess that for me is a good practice. I wouldn't stay in a project/company where they have the policy of pair programming always for each project (they exist). I need my space working, but every now and then I think it's a very good practice for me and the project.