Pair programming is exhausting and definitely not for everybody and for every single day. But. This is still the best way to exchange knowledge and produce co

Pair programming is exhausting and definitely not for everybody and for every single day. But. This is still the best way to exchange knowledge and produce code when normally you would need a code review. Pair programming is not a waste of time. It does not cost twice as much -- it actually costs less. It costs less because having another person working with you cuts all the procrastination and keeps things in focus. It costs less because now you have to discuss every part of the design with another person which is likely going to lead to better design. It costs less because if one person doesn't know it or spot it, the other person will. It costs less because you get immediate knowledge transfer and two people who can continue the project. Things can continue moving forward even if one person gets sick or leave the project. It costs less because people learn new stuff crazy fast when they can observe other person doing things they don't know. It costs less because actual people (like me) like to work with other people. It is fun. It costs less because code review is a shitty process where 99% of people fake they made a review and only pick on stuff that immediately stands out rather than actually trying to thoroughly understand and analyse the change. Unless you have a brilliant developer that can do everything by his/her own with no help or review. Consider yourself lucky.