[superuser2]

Remote work is an excellent paradigm when you get an assignment, go work on it for a while in total independence/isolation, and then turn it in, i.e. when developer-hours are perfectly commoditized. Not every software project is like this at every part of its lifecycle.

The same pitfalls that apply to outsourcing to low-cost-of-living countries should apply to hiring American remote workers: communication overhead, lack of context and understanding of what the product should be, etc. If a projects works well with remote workers in developed countries, consider that it's probably irrational and a borderline violation of fiduciary duty to pay extra for them rather than equally skilled workers in India/China/Eastern Europe.

[jonesb6]

I wouldn't forget that communication is deeply entwined with regional culture. I would argue that it is much easier to hire a remote worker from the same country then it is from a third world country (which are frequently known for remote work). Everything from time zones, work hours (say western European countries accustomed to ~5-7 actual work hours /day), laws, religion, etc.

[alkonaut]

Yes, one shouldn't confuse outsourcing and remote work: with remote work I mean people working in the same tools (version control, issue tracking etc) in the same time zone (+/- 1 hour), and being always available on chat/voice/video and occasional physical meetings.

Most people who work in a multi storey office communicate the same way with the people on a different storey as they would with people in a different city.

[amorphid]

I work in an office, and everyone on my team is remote, including my boss. I might as well be working from home most of the time! But I like going into the office :)