Skip to main content

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams.

If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming. 

Since these tools are for gamers, they have to be
  • fast (low latency)
  • light (as not to steal CPU-cycles from heavy games graphics) 
  • moderate in bandwidth usage (as not to affect the game server connection)
There are several options around: TeamSpeak, Ventrilo, more recently the massively grown Discord, and finally Mumble, which is the open-source alternative of the gang.
A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSpeak server set up between them to allow voice chat during online gaming sessions (great team building option for distributed teams, by the way).

As the team was growing, we began experimenting with using this service for team communication in between meetings (we switched to Mumble at some point, so I'll refer to it as Mumble from now on).

File:Metromumble dark preview.png

Mumble turned out to hit a pretty sweet spot compared to our conventional video conferencing software (we use BlueJeans):

A video conference needs many clicks to fire up and get everyone dialed in.

Mumble, on the other hand, has the team constantly connected, so there's one click required to start speaking.

The usual scenario would go like this:

1) I ping someone on IRC, asking a question
2) We go back and forth in writing for a few lines
3) One of us would ask "mumble?"
4) We both un-mute ourselves in Mumble and start speaking
5) Others may listen in, and join the conversation if they feel like it, or move to a Busy channel if they want to focus on other work.

The video conferencing software will take up all bandwidth and resources

Being optimized to imitate physical presence, the video conferencing software will exploit your laptop's resources to max quality, sometimes with devastating effects (especially on Linux).

Mumble, on the other hand, sacrifices video completely and focuses on voice only. It is optimized to save resources, so you barely notice it is running.

Video conferences will not work for poor connections (or require you dial in via expensive phone numbers). 

Mumble on the other hand, works excellently on poor connections. Latency is marvelously low, which can be tested with the "ping pong test":

1) You say "ping"
2) The other person says "pong" when they hear you
3) You say "ping" when you hear their "pong"
4) Repeat until you get a feel of how long a roundtrip takes

In our video conferencing system, a roundtrip takes about 1-2 seconds (!).

In Mumble, it's like being next to the other person You can barely notice the latency, even when speaking to colleagues halfway around the world (last Friday I did the ping test with one colleague in Yekaterinburg and the other in India).

I think this difference in latency may have a HUGE effect on natural discussions in larger distributed groups, but that's a theory for another day.

So, as it turns out, the things that make gamers love Mumble may also let distributed teams love Mumble.

If you want to try this out with your team right now, you may be better off just starting with Discord, as it is a free and no-hassle setup. At eyeo we are pretty adamant on things like security and privacy, however, so we're glad we can use the awesome open-source Mumble on our own servers.


Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration