3 ms·
Your company has to have the right culture for this. Companies like this are rare. Most just assign whatever's in the queue to whomever's going to take it, mean
by nunez 9y ago
Your company has to have the right culture for this. Companies like this are rare. Most just assign whatever's in the queue to whomever's going to take it, meaning that everyone has "something" to do at all times.
- meuk 9y agoUgh, yeah, this is horrible. Especially if you're at a company which doesn't have any documentation, and the rest of the team is in another country with 3 hours of time difference, so you're on your own after 3PM.
- crdoconnor 9y agoCompanies that permit pairing are not rare.
- nunez 9y agoThey are in my experience with several large corps.
- a-priori 9y agoI think the critical aspect here is the management system. Pair programming makes total sense when tasks are owned by the team. In that case it's in everyone's interest to improve the team's overall velocity. That means time spent mentoring juniors or working together on tasks is well spent. When tasks are owned by individuals, it's in everyone's interest to increase their own velocity which means maximizing time spent working on their own tasks. People are disincentivized from helping other people complete their work or mentoring them, because that directly reduces your personal velocity.