[throwawaycopter]

> Face to face collaboration is a lot more efficient.

That's really not my experience. I'm always very confused when I see this statement being thrown around as if it was a universal truth. Perhaps depends on your role?

Honestly, for all the companies I worked in the past decade, the ones where I had better quality communication were the ones where I worked remotely.

Then again, I'm a software developer. Developers tend to be good at communicating through pull requests, documentation, screen sharing and text-based chat where you can send snippets.

[slotrans]

> That's really not my experience. I'm always very confused when I see this statement being thrown around as if it was a universal truth.

Because it's obviously true.

Communicating through pull requests is shockingly inefficient. It can take days or even weeks to accomplish what face-to-face communication would accomplish in SECONDS.

[dudul]

Please explain with a case study or an example.

IME face to face communication gives the impression that communication happened. The impression that a problem was discussed and solved. When talking people barely listen and just wait for their turn to speak and feel like they are contributing.

Written communication can be re-read, it can be looked at your own pace when you're focused. It can be challenged with comments and it's much harder to hand wave the questions away.

[slotrans]

I honestly don't know why I have to explain this, it is, as I said, shockingly obvious.

First, the mega obvious: if I leave a PR comment, and you ignore it for several days, resolving the conversation will take several days! If I walk over to your desk and speak to you, now, that doesn't happen. Especially if we resolve the issue while I'm standing there, and I watch you type "git push".

Moving on...

In a Github PR (perhaps other interfaces are better!) you cannot comment on a line that wasn't changed. This can make it very difficult to point out problems caused by the way that added/changed code interacts with code nearby. It forces the reviewer to describe an outline of the issue, or paste bits of code and mention line numbers. It's possible to do this well, but it takes focus and clear writing. Folks who are not good writers, or who are communicating in a second language, struggle mightily with this.

...but if I can walk over to your desk (or you to mine), where I can point at the nearby code with my finger, there is no ambiguity. No need for careful English composition. No back-and-forth. I just point.

Honestly, have any of you in this thread ever had a face-to-face conversation?

[ipaddr]

Why would a face to face conversation help? A smile is going to suddenly explain why you using a 7 character variable is jeopardizing the project? People are so afraid to confront others in person so if you talk to them they will just accept your changes so they don't have to deal with the person breathing on them anymore? I can see that..

[throwawaycopter]

As I said, this makes me very confused. Face to face communication tend to be absolutely inefficient in my experience.

They are a hindrance more often than not.