I moved from a developing country (where I worked 1 year in a software dev environment you describe) to the UK. So I know exactly what you are talking about. F

I moved from a developing country (where I worked 1 year in a software dev environment you describe) to the UK. So I know exactly what you are talking about. Feel free to pm me if you have more questions List of issues I can think of... 1- In some cases, people in developing countries usually have a short term thought/goal. Like myself. I'm just here until I can apply for Masters in xyz country or immigration to lala-land and get out of here. Brain drain is very very real and very very obvious. People change far too quickly. And because there is no handover/software dev process. A lot of stuff is re-done. 2- We just have never ever seen good practise/experience to know any better. In the UK, there were people next to me who had been engineering for 20+ years! I didn't have access to that level of engineering/experience. I'm talking about Engineering, 20 years of coding/design experience of building/shipping stuff. The senior guys are still there. They just drift to management as engineering is dirt cheap. 3- I'd recommend listening a lot at first. There will be one or two good people who others in that team will be looking up to. Focus on those guys and explain your changes to them. They'll explain it to their fellows in their language. And there will be quiet people mostly because of language barriers. 4- Take baby steps. (or one big drastic step) 5- We don't think in English. That becomes a problem at times because people in English speaking countries think in English, learn code in English, speak in English etc. We might know English. And we write text/code in English. But we actually think in our own Mother tongue. Hence the focus on convincing a few key people who others are looking up to. And then they can talk in their language. 6- Build trust 7- Sometimes the gentle approach doesn't work and you need to use the stick approach. This is how its going to be done. The CI system is going to enforce this policy. I'll do all merges and this is the list of things you need to make sure work before sending a PR. 8- Establish your role with the CEO and make sure the CEO communicates everything to the team. Including the fact that there will be some time invested in improving software methodology itself. Otherwise, you'll be in a constant battle for justifying things. 9- In the developing countries, overall, people are in a higher stress state. It can be any number of things most commonly financial stress, family social issues, marriage issues. 10- Age matters here. Not technical/expertise. And if a bunch of people came from one University and another bunch from another, it matters. 11- Notice who eats lunch with who. 12- Build trust. Learn a few words of the local language. Try to say a few words. This usually results in a bout of laughter though. I can probably go on n on. But I think you have enough