I prefer pair programming over code review.

I find it annoying as shit trying to code with someone looking over my shoulder

They are not mutually exclusive

@unsignedint if that’s how you see pair programming then my condolences.

@rooter yeah you can improve communication among team and also when someone switch jobs or go to vacation there is someone that can replace him in some way.

Unfortunately from management perspective it looks like they’re paying twice for same job. They treat programming like working in factory from 8 to 5.

@vane you're right about the management perspective. But what that fails to consider is that you're actually having two people doing half the work. Plus the double the bus factor for most companies

@korrat I can only write it from my experience. I was hired once as independent consultant and started pair programming. Manager talked a bit that he won’t pay for same work twice but I ignored him as I got hired by his boss. After this type of work started to pay off and project speed up he stopped saying anything. From 100 issues in 2 weeks we went into talking and joking because problems got resolved. The best is I was mostly not coding but trash talking and joking all the time.

That happened to be next problem - we worked to good and people complained that they need to focus and got to much work and team that I introduced pair programming was not working but only joking and it annoyed them.
I left company after we put product live.

If you can’t find cool people around no methodology will help but I found pair programming to be best of all as it opens mind that programming can be cool.