The long way through Software Craftsmanship

Pairing with junior developers

Feb 3, 2015 - 2 minute read - Comments - pairingpair-programmingexpertisejuniorseniorexperienceapprenticeship

After reading this blog post, here are my thoughts:

WARNING: the post was about how to do it, these reflections are on a more philosophical level

This is a controversial topic, as:

  • You cannot discern how much or little the other person knows more than you. I cannot find the reference anymore, but it was a to the tune of “once the other person’s level is higher than yours, you cannot know how much”
  • There are different knowledge areas. Yours and theirs might overlap on some areas, but not completely. So they may be experts on an area that is not useful to the technology you’re currently using.
  • Different people have different passions and motivators.

When and where are you a junior and a senior?

  • Does it depend on each job?
  • Is it on each product you work?
  • Is it on each team?

“when you join a new project you are starting from square one”

D. Hoover, A. Oshineye in the chapter Sweep the floor, Apprenticeship patterns

Related to the amount of senior people, is there only one senior per team?

  • Can everybody be a senior? If we assert this is true, what about “if everything matters, nothing matters”. Does that mean that everyone is senior or there are different levels of seniority and we call “the senior” the one on the top of the list?
  • Who choses the senior within the team? Is it self-organized, self-chosen? Do the people chose one? Is a shared responsibility, as each one masters a (possibly different) subject?

Food for thought.

What do you think about it?

Book: Diseño Ágil con TDD (Spanish) Open discussion: On code reviews

comments powered by Disqus