I don't have proof, but I have empirical evidence that this is true:
▫️The outcome of a pair programming session is directly proportional to each developer's capacity to challenge each other.
Let me explain: 🧵👇
▫️The outcome of a pair programming session is directly proportional to each developer's capacity to challenge each other.
Let me explain: 🧵👇
If you pair 2 developers with very different seniority levels, the session will become more of a training opportunity for the least senior person.
The short-term impact on the project will be negligible. Most of the ideas and progress will come from the senior person.
👇
The short-term impact on the project will be negligible. Most of the ideas and progress will come from the senior person.
👇
If you pair two developers with a similar experience, their contributions multiply, giving you a much larger short-term impact.
You aren't getting ideas from one or the other anymore. You are getting a polished version that's better than any idea individually.
👇
You aren't getting ideas from one or the other anymore. You are getting a polished version that's better than any idea individually.
👇
Again, not proof that this is the case. This has been my observation over 20 years of using pair programming.
I'd love to hear what some of the people that have studied this before think:
@macerub
@dmokafa
@mcsee1
@MattCodeJourney
@KentBeck
@unclebobmartin
@Grady_Booch
I'd love to hear what some of the people that have studied this before think:
@macerub
@dmokafa
@mcsee1
@MattCodeJourney
@KentBeck
@unclebobmartin
@Grady_Booch
• • •
Missing some Tweet in this thread? You can try to
force a refresh
