Skip to main content

Quick thoughts of working in a multilingual team

I've been working as a part of international team for about six months now. By international team I don't mean that the team is located in two or more locations but that the team consists of people of different nationalities and therefore different languages. I thought I'd write down my thoughts on how that's working out.

The team 


About half of the team are from Finland and half from India. As the mother tongue of the team members varies the teams common language is english and it works out just fine most of the time. The language barrier does bring it's own challenges, here's a few that I have noticed or been informed of.

Challenge with conversations


Mostly out team struggles when it comes to ad-hoc conversations on implementation details or architectural decisions when we, the finnish team members, start to talk about it, in finnish, and thus leaving half of the team out of opportunity to join the conversation just because were talking in finnish and they have no idea what we're talking about.
This could be resolved by speaking only english when the topic is work related but to me that feels unnatural. Because it feels unnatural to speak english to another finnish speaking person it's probably why it's also so hard to remember that we should be speaking english.

Challenge of understanding


Another thing that happens occasionally is misunderstanding. Everybody is speaking english that no one speaks for a mother tongue sometimes leads to situation where a message might get misunderstood at the start or along the way as it passes from person to person.
It's not a huge problem as we tend to keep our individual tasks small but it does create some extra work in a form of refactoring or rewriting code. This does happen also when people have the same mother tongue but not as often.

Conclusion


Overall I don't see big problems working in a multilingual team but this is my first time as it probably is for some of the other team members also but it does bring some challenges. Hopefully we'll get better at it over time.
At least the next time I join a multilingual team I'll have a better idea what to expect and hopefully some solutions on how to over come or reduce the challenges.

Popular posts from this blog

Simple code: Naming things

There are two hard things in programming and naming is one them. If you don't believe me ask Martin Fowler https://www.martinfowler.com/bliki/TwoHardThings.html . In this post I'll be covering some general conventions for naming things to improve readability and understandabilty of the code. There are lots of things that need a name in programming. Starting from higher abstractions to lower we need to name a project, API or library, we probably need to name the source code repository, when we get to the code we need to name our modules or packages, we give names to classes, objects, interfaces and in those we name our functions or methods and within those we name our variables. Overall a lot of things to name. TLDR; Basic rule There's a single basic convention to follow to achiveve better, more descriptive naming of things. Give it a meaningful name i.e. don't use shorthands like gen or single letter variables like a, x, z instead tell what it represents, what it does...

Simple code: Integration tests

Integration test is something that tests a functionality that is dependant on a external system e.g. a database, HTTP API or message queue. Integration vs unit tests The line is thin in my opinion. The integration part can be faked or a embedded services can be used in place of the actual integration point and with these solutions the interaction with the external system is bounded in the test context and the tests can be executed in isolation so they are very much like unit tests. The only difference with this type of integration test and unit test is that the startup time of the embedded or faked system usually takes some seconds and that adds total execution time of the tests. Even though the total test exection time is longer all the tests need to pass and all the cases need to be covered whether there's external systems involved or not so the importance is equal between the test types. This is why I wouldn't separate unit and integration tests from each other within the co...

Simple code: Simplicity

Simplest solutions are usually the best solutions. We as software developers work with hard problems and solve a lot of small problems every day. Solving a hard problem itself is a hard job. Though in my opinion it's not enough to solve a hard problem in any possible way but a hard problem should be solved with a simple solution. When a developer comes up with a simple solution to a hard problem then they can declare the problem solved. First a disclaimer. Coming up with a simple solution to a hard problems is itself a very hard problem and takes a lot of time, effort and practice. I've seen my share of "clever" solutions for hard problems and the problem with those is that usually the solution itself is so hard to understand that depending on the size of the problem it may take a developer from hours to days or even weeks to understand how that "clever" solution works. It's a rare occasion when a developer has come up with a simple solution to a hard pr...