I suppose you could describe it that way. Pair programming certainly isn't for everyone, but under the right conditions, it can be very effective. It can be a g

I suppose you could describe it that way. Pair programming certainly isn't for everyone, but under the right conditions, it can be very effective. It can be a good means to share ideas and keep up the motivation. That said, it ultimately comes down to whether or not the pair work well together — sometimes you 'click' and everything's great; other times you don't. A related technique that's quite interesting is mob programming, where an entire team is huddled around a workstation. There's less pressure on each team member as individuals, and the person typing the code is mostly following directions from the others. Really, the approach to development needs to be appropriate for the dynamics of the team. It might be a good idea to at least try out pair or mob programming to see how effective it is. But you can't just be doing it just because it's the 'hip' thing these days. Also, pair and mob programming can be quite draining, so you may not want to be doing it all day. You could do it for part(s) of the day, and work on your own at your own pace at other times.