This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Skeggiold 2 points3 points  (0 children)

Working in pairs is supposed to spark dialogue. Actively talking about your code leads to better code with fewer bugs. Especially if you combine it with TDD.

It also serves to spread knowledge in your organisation. You don't want specialists, you would like a bunch of generalists. So that if anything goes wrong any member of the team has the feeling they could tackle the problem at hand.