2) Language barriers Language is not an overwhelming barrier for a technology professional if approached correctly. Assuming you need to learn a major western

2) Language barriers Language is not an overwhelming barrier for a technology professional if approached correctly. Assuming you need to learn a major western European language, a good rule of thumb is 250 hours of work to become sufficiently conversational for shopping and travel, and between 500 and 750 hours to defend an opinion coherently on a day-to-day topic. (For a totally unrelated language, multiply by 4.) You'll still be at a linguistic disadvantage, but you'll be able to pick up the phone and deal with confused customer service representatives or whatever. Real ingrained fluency and an educated vocabulary takes longer, but most people are in excellent shape after a couple of years of immersion and a bunch of reading. On the professional side, most HTLAL readers will be able to find jobs using large amounts of English. French programmers, for example, tend to read English fluently, attend talks in English (even at French conferences), and write some fraction of their code in English. I learned this while trying to improve my technical French—I went shopping for French programming books, French programming podcasts, etc., and I would up finding (a) very few technical books, (b) French programming news aggregators with 60% of the links in English, (c) French programming conferences where every single speaker spoke English, and (d) lots of very friendly French programmers with English skills ranging from serviceable to excellent. If you want to live in another country for a while, don't let language be the factor that stops you.