I think pair programming can be great, but the secret is that it has to work for everyone who wants to do it. I like to work by myself sometimes so I wouldn't want to do pair programming everyday, but sometimes it is helpful especially when getting a project off the ground. When two developers are working together like that, you can branch away by establishing clear areas of ownership and then popping off and working on those areas separately, then consulting again when it is time to merge them together.

yeah that makes sense! it's great for sharing knowledge at the beginning, and we've been doing it a lot cause we're doing a new project this month. once the amount of new stuff getting added slows down then i hope we can go back to regular work.

if u made a game about golf you'd be par programming

I'm a bit skeptical myself whether it's really worth it. It's roughly double the effort, but for what gain? For something tutorial like or educational I can see the benefits (well-managed group work is usually beneficial), but the way pair programming discussed is, like, always evidence free, seemingly reflecting aesthetic preference or social style more than anything. Which is not to poopoo either of those completely, it's just rather a beginning than a conclusion.

I made robottic fruits you can control with an Arduino. This allows pear programming.

I devised a system to control the level of carbonation in mineral water. I call it Perrier programming