Pair programming

Recently I met the "pair programming" term, which refers to two developers working together in the same task. 
There are plenty ways for this to happen. The most common though is that a developer writes code, whereas  the other shares ideas.  

The more you pair programming, the more familiar with it you become

So what is pair programming all about? What do we achieve?

• The code that has be written and have been analyzed by two developers, is more likely to have less bugs. 
• Being alone and write code for a hard task, often takes more time than being with someone else.
• The code style varies between developers. Often pair programming has an outcome that developers over time start coding almost with the same style. You can imagine the benefits of it. Right? Think how you have been troubled and pulled your hair off when you had to read a part of a code that you couldn't understand. 
• Code never feels like a competition anymore

In case there are two different ideas for the same task, remember that code wins arguments. So, take your time and develop your idea. Then give time to your peer to develop his/her idea. In case both of ideas are good enough don't hesitate to accept your peer's idea.