You have to think about it differently than "Oh, we go here for meetings". It's more like a watercooler -- pop in every now and then and see what's going on.
I blogged about it a couple of months ago: http://cafbit.com/entry/hanging_out_on_the_job
The real juice is removing the friction to communicating. You don't want to be scheduling conference calls or chatfests. You want to be able to click see if Bob's available, click into his space and say "Hey Bob, got a minute?"
There should be at least one "water cooler" room where people are free to share youtube links or BS about non-work stuff. In short, the chat system becomes the virtual office. The team room becomes the virtual shared room where anyone can jump in on a conversation that interests them, or start one up casually.
The company MUST have a day to day internet communications based culture for a remote team member to be successful. If a team has a key remote member from the start it's easier. All remote teams are of course the easiest.
It's hard to add a remote member to a team that is used to being in the same offices. A lot of people will resist changing the entire culture for one "new dev". Office members will talk about a design problem at the physical water cooler instead of the virtual one. The on site team will go for beers together after instead of having a couple on a google hangout/skype video chat. The remote member will feel more like a contract dev assigned work than a creative member of the team. This is no good.
Where I've seen adding a remote member done successfully, requires management and team buy in of remote working. The manager/team lead should work a few days a week, or even a week a month, remotely. So should the other team members. After the team lead sees what it's like to be the lone person on speaker phone while everyone else is in the meeting room, you understand why if a remote member is in the meeting, everyone should be using skype/google hangout for it. The offices should become more of a shared coworking space that happens to have your company name on the door.
I myself prefer to work remotely. It's not for everybody or every company though. For a startup I think a remote culture from the beginning makes a lot of sense. Unless you require it to show off to investors/clients, skip the office. Have the cofounders work from home. Meet up atleast once every 3 months in real life for beverages and discussion. Talk on chat, every day. That's my thoughts.
One last thing worth mentioning, chat logs are great for when the new guy wants to understand a design decision. Why did we use $nosql instead of $nosql2? Here, read the logs from 6 months ago. For operations events (downtime etc) the timestamped chat logs are great for after action reviews. Can you brainstorm better in a physical room or a chat room? I've found the ability text chat gives you to allow everyone to talk at once, without talking over anyone, allows for discussion to proceed at a more rapid pace and more paths followed. This can be of course good and bad, such is life. :)
I disagree with that. We had the first real in-person meetup about half a year after I joined the company. Up to that point, I knew everyone else pretty much only through text chat (Google Hangouts didn't exist yet).
But when I met everyone in person, it felt like we already knew each other quite well. It may not always be the case that your online and real-life personalities are aligned enough to get to know a person via chat, but in this case it definitely was.
To what extent do you think this is the case?
Github are a distributed team, Digg's programmer was a remote employee (from elance IIRC). Linux would be another biggie.
But things are different if you want to build the next big thing with cofounders and there I experienced three big disadvantages:
1. All big (and finally successful) ideas and ventures were born by sitting together, day for day. By being forced to stay together in one environment. And we haven't born those great ideas when we had meetings about our products or were specifying some API, no, it was always when we were jabbering around doing silly things. You won't get breaking ideas on Skype or Google Hangout, believe me. Maybe a group of people needs sometimes a kind of antogonist or some constraints to get even more creative and if it's just some "we have to share our workday together."
2. Just working alone and from time to time a face2face meeting won't establish a relationship which you definitely need to overcome conflict situations. You can't build real relationships at some artificial situations like meetings or team off-sites while usually working all the time alone. Once you have a severe conflict and you have missed to build a relationship before odds are small that you get things working again (or even a normal conversation). A lot of people are the type "forever gone", leaving the non finished code base untouched forever.
3. You have to be positive and think that everybody will contribute in the same manner and quantity as you but some are not able to do this because they are heavy procrastinators when left alone or just not persons of integrity. If you have somebody who is ambitious and is in control of his time and energy, great! Jackpot! But the probability that you end up with a procrastinator, somebody who never finishes something or somebody who quickly looses motivation (or is just depressive) is not so low as you might think and you hear crap and other excuses every update meeting like 'oh I couldn't do this because I had to reinstall osx and xcode blabla and the gem sucks anyway' or whatever. Some freelancers invoice the same time many times to many clients, just remember this guy recently outsourcing his work to some people in China. You never know who you work with and what the person is really doing if you do not know them too well. I know that freelancer could also do this shit onsite (you cannot watch their screen 24/7 and check if it's really your source they are working on) but being together in one office lets the person focus more on your work and your environment and they are not distracted by other potential projects or ideas. And integrity/work morality increase.
So, it's hard to say if remote work is good or bad. But to sum up, I feel that when working as freelancer for a client then try to do this remotely. As a dev I would try this, as a client of course not. But if you want to start something great with friends or just met new cofounders you have to be together for some time.