📎 Webclip
I don't really like pairing (but I want to)
The author describes repeated attempts at pair programming over several years that felt unhelpful, unenjoyable, and exhausting compared to working alone. They contrast their own frustration with the enthusiasm for pairing expressed by many trusted peers, explore several possible explanations, note that they enjoy pairing in a mentoring context, and end by asking the community for suggestions and pairing opportunities.
Reading notes#
- The author has tried pair programming many times and consistently found it less helpful and enjoyable than solo work.
- They feel they learn more when working independently and experience pairing as tiring.
- They are often frustrated when a pairing partner cannot match their speed when they feel in a strong flow state.
- Enjoyment of listening to music while coding is another reason they dislike pairing, since that habit does not fit well with working closely with someone else.
- This experience conflicts with the opinions of many trusted colleagues who describe pair programming as almost magical.
- The author wants to enjoy pairing but does not, and starts examining potential reasons for this mismatch.
- One hypothesis is that they might simply be bad at pairing, since it is a skill that requires practice.
- They mention efforts to improve at pairing, including reading about it, watching videos, and pairing with many people, but their feelings have not changed.
- Given the positive views of people they respect, they consider their lack of skill the most likely explanation.
- Another possibility is that they have not paired with the right people.
- A key frustration is having to slow down and interrupt their sense of flow to explain things while pairing.
- In most pairing situations they have been the more experienced developer, which might affect the experience.
- They suggest they might enjoy pairing more if their partner were more experienced or at a similar level.
- They acknowledge that pairing with less experienced developers may require giving up their preferred flow in exchange for other benefits that are not very clear to them.
- They also consider that pair programming may simply not be enjoyable for everyone, including themselves.
- The industry’s strong acceptance of pairing’s benefits creates pressure, because not enjoying it could be a long-term disadvantage.
- They observe that many teams treat enjoyment of pairing as a proxy for team fit, which worries them.
- They fear ending up as the odd person out if they do not enjoy pairing but cannot dismiss this possibility.
- They note an exception where they do enjoy pairing when the goal is to help someone else learn or solve problems.
- The author recalls enjoying a stint as a mentor at Dev Bootcamp, working a few hours after work to show Ruby techniques and help students with difficult issues.
- They also like a mentoring-style role at work with less experienced developers.
- Their negative feelings about pairing arise mainly when working on tasks for which they are directly responsible for delivery.
- The author reiterates that they respect people who strongly advocate for pair programming and want to share in that enjoyment.
- They ask readers for ideas on how to get better at or enjoy pair programming more.
- They invite others to pair with them remotely on open source Ruby or Elixir projects.
- They mention using Screenhero for remote pairing but are open to terminal-sharing tools as well.
- They quote the XP idea that if something hurts, it should be done more, applying this to pairing.
- Readers are encouraged to contact them by email or Twitter if interested in pairing.
- The author notes that scheduling may be challenging because they have a new infant at home, but they believe it can be managed.
- They express special interest in pairing with developers in Africa, having heard positive things about the community there.
- They hope pairing with people in Africa can broaden their understanding of that part of the world.
