Translations:Collaborative programming/13/en

Here is a suggested setup for a collaborative programming session. If all of this seems too rigid, skip the recommendations, and do your own thing: meet and show each other your code and talk through it, what matters is that you collaborate in the process.
 * 1) There are no rules, there is only a set of recommendations.
 * 2) It’s not a requirement to join the session that one knows the codebase or a specific language because you will be working as a team (a group of two to five people) who meets for a call.
 * 3) One person is always leading the session for a while and sharing their screen and is implementing one small step of a problem that the group wants to solve together, let's call that person the writer.
 * 4) One other team member is the "researcher" that asks curious questions and suggests things to try and implement that could be one step of a solution.
 * 5) If you have a nice pair programming tool setup that’s great, so different people can be active, otherwise the one that shows their code, the writer, can be following the instructions of the researcher
 * 6) What's most important is that the researcher role is being handed over every 10-15 mins.
 * 7) Being the writer make sure you describe what you are trying to do while you write and as an observer make sure you stay engaged and ask questions about things you are unsure about.
 * 8) At any point, people can ask questions and ask for help from the team for looks up things in the docs ask for ideas about what to do next.
 * 9) As the researcher, if there are people in the team that have less experience than you make sure you keep them included by asking little questions: "What should we do next?" or "How can we solve this?"