Who thinks about collective programming?

Question

Python

Now I am looking for a person (Python) who would be interested in coding an arbitration bot together
for bitcoin exchanges. There are already raw raw materials - it remains to digest and finish them.
The question is this - it is interesting to code alone, but together it turns out,
as a rule, (for me personally) to work much faster.
When working, any communication medium (Skype, Gtalk)
and desktop viewing (VNC, TeamViewer etc) is used.
As a result, we get a better code, in terms of architecture,
since two heads are better than one.
How are you doing with this?

Answer 1

There was a practice of working in pairs:
One sits at the keyboard, the second is nearby. We change every hour.
Bottom line: cleaner code, but the amount of code per day (and, accordingly, the number of tasks performed decreased in relation to two working in parallel.)
We came to the conclusion that it is better to code in parallel, but to make revisions to someone else's code (at least once a day).

Answer 2

It is only necessary that these two were friends or good acquaintances.
Otherwise, their disputes will lead to conflict and to the fact that only one of the two will start writing. And the second will not care about the code.
And yet it is better to work directly together, and not remotely via Skype.

Answer 3

I had experience in programming in pairs. At first we sat at each other's heads, as the jimpanzer described above, but the work is really slow. Then we switched to the unix-way, i.e. distributed tasks according to the principle one script performs one function. so many files were born, which then had to be revised and renamed, names and calls were standardized. As a result, it is possible to work in pairs, but you need to agree on a lot of things and calmly and constructively approach the issue of changing agreements. Without a great desire to achieve a common goal and the ability to compromise, working in pairs is not realistic.

Answer 4

If two programmers are mature and independent, then in my opinion the best thing is to first agree on the project structure, draw class diagrams, and other diagrams as needed, and let each one code his own piece, looking at the entire project from time to time.
Programming in pairs is needed when the level of one greatly exceeds the level of the second, then programming in pairs will quickly bring the beginner to a new level, and begin to give small independent tasks. There is a plugin on this topic www.opennet.ru/opennews/art.shtml?num=36979 (I haven’t tried to use it, but it’s quite a useful thing for this technique)