Second there are no radically different timezones within the US. If you're on the east coast you work most days from 10 - 6, if you're on the west coast you work most days from 7 - 3.
Third if you're working on something pressing with your distributed team you schedule some time together to work later. If you're on the east coast you may have some nights during a sprint where you're wrapping up at 9pm or 10pm.
Fourth no matter where your team is located if you have members in different US (or even international) timezones you want at least 4 hours during the day spent together (employees are really only performing at the top of their game for a fraction of the day anyway [2]).
[1] A truly distributed team is one that supports remote workers via communication and culture as much as they do their local employees.
[2] http://cs.stanford.edu/people/eroberts/cs201/projects/crunch...
What frustrates me about remote workers is they cluster around eastern europe or india/china with main offices in the USA. They're all hugely different time zones.
I think remote workers who are in the same time zone area as the main office, say north or south america, might work better. But I don't know because I haven't had a chance to work on that kind of team.
The bandwidth of personal IRL interaction adds enormous value. Yes, in many scenario's that value is not strictly necessary, or can be compensated.
But if you think it's bullshit, or something for "dinosaurs", you have a serious problem. Not just as a programmer, but as a human being.
To be fair I never said real-life face time lacked value. I think periodic group meet-ups are helpful and need to happen. I think you were reading words I never wrote. I think ideally a distributed teams do need to have retreats together. (This is a "like milkshakes, but do I need one everyday for lunch" kind of thing IMHO)
>How is it that every time someone makes this argument, they do it in such a superficial, arrogant and ignorant way
I was addressing the authors point that: the way to to address this "scarcity" is by importing people from over seas into a few major metro areas. My point is if there are many domestic (or foreign) resources outside of said metro areas there isn't really more then a self-imposed scarcity.
>you have a serious problem. Not just as a programmer, but as a human being.
I was sharing an opinion-- I am totally OK with you disagreeing with it, that is fine, but that above response was beyond rude, it was personal and cruel.
For many (most?) startups in the valley, if you aren't living in the greater SFO area, or willing to relocate there, they are not interested.
They are dinosaurs living in the past, fighting distributed collaboration. (Which is ironic as they are technology companies). Importing people from overseas to the bay area is actually the hard way of solving the problem.
From first hand XP, I can tell you going distributed has made hiring top notch talent 10x easier. And if I hire someone overseas, they don't have to move...
Again, IMHO all the excuses like "culture" are bullshit, if your culture depends on holding hands as a group every day, your company culture is already fatally weak.