|
|
|
|
|
by DoreenMichele
2899 days ago
|
|
As someone who does a lot of remote work -- though I am not a programmer -- I will suggest that communicating remotely is different from doing so in person and many people suck at it. This is a serious problem if you are going to work remotely. Time difference can be an issue as well. When I had a corporate job, I knew a woman at this American company who was managing a remote team in India and, when things went wrong, she got phone calls at 3 a.m. The company did about 3/4 of its business in Japan and the CEO split his time between the US headquarters and Japan. They also had probably the world's most amazing teleconference setup that I have never seen a write up of anywhere. Among other things, the huge time difference was challenging to deal with. Also, you need to be able to embrace diversity and multiculturalism. This is not easy for most people, as evidenced by the ongoing cries of racism, sexism, etc in the world. People tend to know how to deal with folks "like them" and not be so good at dealing with people who are different. Even if they aren't intentionally excluding "others," it tends to have the effect of excluding them. Multiculturalism is a hard problem to solve and you have to solve that if you want remote first policies, IMO. |
|
The second issue seems to be due to a lack of autonomy on part of the engineers in India. It seems they had a satellite office in India and the Indian workers themselves lacked autonomy to act in case something went wrong. What was so good(I guess you are being sarcastic) about the teleconferencing software?