I have always worked remotely. My company works this way, my employees work remotely. IMHO it is not hard or difficult per se, but you need to design your company around it, like with other things. It is also an area that needs more study in order to develop fully. Probably if I had a conventional company and I had to transform or convert it to remote, it wouldn't work. There would be vested interest against the conv…
Why Remote Engineering Is So Difficult
41–43 of 43 posts
Re: Why Remote Engineering Is So Difficult
#42In a former life as a corporate software developer, I distinctly remember having to get up at graveyard-shift hours to infrequently coordinate with some of our Indian team members. Some minimal time-zone overlap is never overrated. I think it is hard to beat real-time communication over chat or voice - asynchronous delays break up any flow in collaboration and turn it more into throw the requirement over the wall and…
Re: Why Remote Engineering Is So Difficult
#43I worked at two companies where everyone worked remotely. I think one of the big differences I noticed is that I never felt like I was that close to the rest of the team. We talked a few times/week through Webex or Skype, but it's just not the same as being there in person. Communication was also a big issue. It's not impossible to have good communication remotely, but I've rarely seen it in practice.
The missing part might have been Empathy.
I was never part of many of the decision-making meetings with the boss and my project manager and I felt like the manager never had our back. After we met onsite for our first bi-yearly 1-week meeting, I realized that he didn't really have any choice in the matter and did in-fact fight for us when these decisions were made.