Social coding rarely means working on the same file at the same time. In order for work to proceed efficiently, there has to be some separation of work and resp

Social coding rarely means working on the same file at the same time. In order for work to proceed efficiently, there has to be some separation of work and responsibility. I do think, however, that this will be great for code review and teaching. None of our developers are in the same place. We use Github and Gists to collaborate, escalating to a MeetingBurner session if we really need eyes on a conflict all at once. Those instances are infrequent, but on the business side, the sales and marketing teams use Google Docs to great effect when collaborating on their documents. The ability to see someone else's cursor and watch their edits in real time is a major force multiplier. Documents reach a final stage much more quickly than they do with the old "track changes and email" approach. I can't help but see parallels in the dev team's approach, even with Git.