Joel’s comments inspired by this retrospective and this comment on the retrospective, plus comments on Joel’s site
There was a slightly tendentious thread on the modperl list on geographically distributed teams a few months ago, started by someone responding to a job posting requiring onsite developers. He thought that managers and companies who didn’t support them were backward, short-sighted and their desire to have people in-house simply highlighted their lack of management ability.</p>
I thought this more than a little insulting but other people responded better than I would so I kept my mouth shut. I think there are occasions where geographically distributed teams can work, but I also think there are many where they simply cannot. And in any case, I think the team members absolutely need to meet face-to-face very three or four weeks for two or three days.
The problem is that you cannot replicate the bandwidth of face-to-face contact online. It's just impossible. For many tasks it's unnecessary -- reporting bugs, posing questions about how a system works, etc. But working closely with multiple people on a large project it's absolutely crucial.
Veering wildly off topic: I also think that in the coming years companies may start to realize the folly of contracting everything out and keeping only static (and normally crappy) documentation as their only institutional memory. Databases and knowledge management systems are well and good, but they can't replicate the logical -- and illogical! -- connections that the best information workers use to solve tasks everyday.