Coding in a Couple
There is an approach to code in a couple in IT world.
What is this?
Coding in a Couple is a technique, an approach when two programmers are coding together at one computer at the moment. One programmer starts as a writer (driver), the other one — as a commentator (navigator). The commentator may truck down all errors the writer made and suggest the best workaround. At the same time the commentator is disallowed to change the code themselves.
A time letter they are changing they roles: the writer becomes the commentator and the commentator starts to write code.
Why do they do it?
Coding in a couple is for better productivity and for faster studying how to code. It is because the very writing code takes about 10% of all time, the others 90% is taken by a search for a better solution.
The writer and the commentator both are thinking about the task together and they are exchanging their thoughts shortly.
Statistics says that those tasks, which takes more than 1–2 days usually, may be solved in several hours if coding in a couple.
So, the pros of coding in a couple
1. The speed of task solving is increasing
2. Less errors left in code while coding in a couple
3. Looking at one is coding the other one is thinking about the coding style of the writer and adopt it
4. Coding in a couple helps to solve such tasks which seemed unsolvable before
And the cons of coding in a couple, of course
1. Coding in a couple is a resource intensive process — it is hard to concentrate for more than 4 hours along
2. Two programmers must have almost equaling qualification to code in a couple
3. Two programmers must be comfortable to each other as being a person otherwise the one could loose the focus and its motivation