Earlier quoted context omitted.
Sococo (I work there) does a good job. Share apps (not desktops); talk and video, pointers and web apps all work together to make pair programming pretty seamless.
Heh, it looks like a game. Gauntlet or something. Strange model to deliberately capture the office layout even. It looks so much like a game of "Cluedo" I'd be tempted to try a murder to see how it worked. "It was Thad, in Patrick's office, with the pistol"
We Tried Building a Remote Team and It Sucked
51–60 of 99 posts
Re: We Tried Building a Remote Team and It Sucked
#52Earlier quoted context omitted.
Even when I was bad at work/life balance when I first started working from home... I still saved an hour-and-a-half each and every day by not having to commute or iron clothes or make my lunch.
I guess that depends on everyone's personal case. But I for one like my commute: 10min by bicycle or 15min by foot, with a nice parc with lots of birds on the way. So in my case, the pros of working from home are almost void compared to the pros of a workplace.
On the other hand, I think besides the commute itself is the freedom you get from not having to constrain yourself to living in places where the commute is doable. I work in downtown Seattle and I would love to move to the suburbs but I'm not sure it's really feasible to spend 45 minutes on the bus to get to work.
Re: We Tried Building a Remote Team and It Sucked
#53An unexpected tool has helped tremendously for our teams in terms of remote work: Mumble ( http://wiki.mumble.info/wiki/Main_Page ). Mumble is a cross platform, open source VoIP application. Often used for gaming in a group (like Teamspeak or Ventrilo). It has the idea of channels (rooms, offices, etc) is very high quality, low latency and low bandwidth installed on your companies servers in minutes, always encrypted…
We're currently in private beta and I'd be interested to get your input on what we're building. We've got a quick walkthrough here https://www.youtube.com/watch?v=KV7HBXuhT7Q and you can signup for the private beta at http://speak.io
Re: We Tried Building a Remote Team and It Sucked
#54An unexpected tool has helped tremendously for our teams in terms of remote work: Mumble ( http://wiki.mumble.info/wiki/Main_Page ). Mumble is a cross platform, open source VoIP application. Often used for gaming in a group (like Teamspeak or Ventrilo). It has the idea of channels (rooms, offices, etc) is very high quality, low latency and low bandwidth installed on your companies servers in minutes, always encrypted…
I wrote a webapp targeted for gamers to easily setup temporary Mumble servers (http://guildbit.com). So I'm sure someone can build a service similar to wrap the Mumble API for workspace users. Similar to Slack with IRC.
Re: We Tried Building a Remote Team and It Sucked
#55Earlier quoted context omitted.
Even when I was bad at work/life balance when I first started working from home... I still saved an hour-and-a-half each and every day by not having to commute or iron clothes or make my lunch.
I guess that depends on everyone's personal case. But I for one like my commute: 10min by bicycle or 15min by foot, with a nice parc with lots of birds on the way. So in my case, the pros of working from home are almost void compared to the pros of a workplace.
Re: We Tried Building a Remote Team and It Sucked
#56Although I disagree with the overall sentiment of the article (remote working doesn't work for generalists). I commend the author for at least trying remote work (especially as a YC company, an organization that openly discourages remote work). Full disclosure, I work remotely and it's by far the best decision I've ever made in my entire life. So to address a few points. Collaboration to me is when a group of people,…
How does pair programming work over chat? I feel like pair programming relies on you both looking at the same code + talking things through while one of you is actually coding. It seems like having to switch over to a chat client to communicate would decrease productivity a lot.
Re: We Tried Building a Remote Team and It Sucked
#57Having had teams that were half-remote before, and all remote now, doing lots of hangouts seems to fill the remote-feels-weird niche pretty well. Just having long conversations in chat tends to not be productive, but you need chat. Something like Slack is a good choice if you can't get everyone on IRC. Somewhat still wanting for better "whiteboard simulator" type options. Ultimately not having an office not only save…
Except that nobody else has a Surface Pro, so the only time I've tried it was with a friend with a Bamboo on the other end. Maybe someday.
Re: We Tried Building a Remote Team and It Sucked
#58Earlier quoted context omitted.
Heh, it looks like a game. Gauntlet or something. Strange model to deliberately capture the office layout even. It looks so much like a game of "Cluedo" I'd be tempted to try a murder to see how it worked. "It was Thad, in Patrick's office, with the pistol"
Yeah some issues with the graphics causing credibility problems. But that's exactly what makes the presence work so well - "Patrick is in Thad's office, and they're both yelling!" Try that with any other tool
No?
Seems odd to use a location metaphor, when online you can be in more than one place at a time.
Re: We Tried Building a Remote Team and It Sucked
#59There's still an issue with timezones but I think the communication/camaraderie problems will be fixed in a VR workplace. This gives you all the benefits of remote and mitigates many of the downsides. If the downsides are sufficiently depressed then many more teams will be able to be remote and distributed and that may have a dramatic effect on society.
Re: We Tried Building a Remote Team and It Sucked
#60What about: Work remote. Get all the company together to a trip to Hawaii each year. I'm sure this can build camaraderie and morale, and I hope someone gives it a try.
http://www.nytimes.com/2015/01/20/business/co-working-on-vac...