The Chinese Contingent

The end of my days with Gopher-Man, et al

Posted by

9

Well, it’s official.  I’m leaving the world of Gopher-Man, Longback Guy, Barefoot Boss, and The Chinese Contingent.  Yep, I’ve got a new job.  I start in a couple of weeks.  I have high hopes that this gig will be a better fit for me than the last one was, though based on the many comments I have received about my Gopher-Man stories, I realize this may be something of a disappointment to many of you.  I’m sorry about that, but I hope to find new characters for you when I begin my next adventure in the world of software (this time I’ll be back in the world of Marketing again, too, which holds a lot of promise for ridiculous work related stories).  I will be commuting into the city again, which should translate into many fun-filled tales of crazy BART interactions or observations, but until then, I leave you with a couple entries from my Blog Spam folder for entertainment.

Comment #1:

“I expect that what you say is true, but which one of us can understand all these changes these days”

Comment #2:

“At the same time my two brothers prayed to Mary, cited saints and periodically wandered into very odd doctrines indeed.”

Enough said…

Translation challenges

Posted by

4

It’s that time again.  I’m in the middle of a deployment tonight – this time it’s not a new software release, but the replacement of a server that runs a portion of the software platform my company is responsible for.  It’s a pretty complicated process, made more so by the fact that The Chinese Contingent is conversing in Chinese in the Skype chat I have going with them.  To keep up, I’m constantly copying and pasting their messages into Google Translator.

Rewind to lunchtime yesterday, at the office.  I ate with Long Back Guy, and we discussed work stuff – no funny stories from him this time.  As I was leaving the lunch room, I said, “I hope things go OK tomorrow,” referring to this server replacement.  He just laughed at me, heartily, as though to say there was no way this would go smoothly today.  Of course, he was right.  We’re having problems as we speak.  Problems I can do little about, except use Google Translator to have some sense of what they are.  The step we’re at right now involves copying data – normally, there is a centralized process we can call that copies all the data we need and we just have to sit and wait around for it to finish.  It takes an hour and a half or so.  This centralized process isn’t working, though, so the guys are copying data for each individual application that runs on the platform.  When the point person handling this was asked how long it would take, he replied with this (Note:  this part was typed in English because the person asking the question asked in English):

there are 39 applications need to do copy

if we figer 5 min for each app, then got 200 min almost

i will update my evaluate, when first app done

So, my task at the moment is to wait for his evaluate.  Since I am stuck translating tonight, I will share the love and give you a different sort of translation challenge to chew on.  Earlier this evening, I got an email about the server replacement (technically called a cutover), and my other half was closer to my computer than I was – I asked her to read the email to me.

There is a  trust from beaver to coyote, I  have confirmed with Mike and we think it should be configured the same way for mouse (from mouse to coyote).  Please ask Frank to do it as well.  We need to make sure that on mouse the following command can be executed without inputting a password:

oracle@mouse:/$ssh oracle@coyote

[Note:  Person and animal names changed to protect the innocent.]  Now, I didn’t give my other half any background before reading this email, and she only got through the first sentence before she looked at me, puzzled, and said, “Is this real?  Is it a joke?”  I said, “No.  Keep reading.”  When she got to the final line, she read $ssh as “Shhhhhhh!”  This was highly amusing to me, though it may not be to you unless you are also a computer nerd.  It is common practice for development shops to give their servers names, and they often pick fairly random classes of terms to use.  In this case, animals.  Our client names their software releases after cars, and their servers after animals – most of the time.

I got this message in a recent email about an unrelated project:

I dropped off the gzipped tarball on nap-happy

I love that sentence, don’t you?  If you are really interested in knowing what it means, let me know, but it’s not actually very exciting at all, and I expect most of you would fall asleep if I spelled it out.  I will say, though, that ‘nap-happy’ refers to a server, so there must be some servers our client has that are named according to emotions – or perhaps the seven dwarves – I can’t really be sure.

I really love broken English

Posted by

6

Maybe that makes me a little weird, but it’s true.  Since I started working at this company where we have lots of employees in China, I have regular happiness handed to me on a plate – well, in email, or Skype, or in meetings, or on the phone.  I’ve pondered why I like it so much, and actually given a lot of thought as to whether this is just plain politically incorrect, but I have decided I just don’t care.  I like it, so it’s good.  A few examples I particularly love follow:

——-

“Sorry for cost so long time since my unclever mind.”

If I tried for a week, I wouldn’t be able to come up with such a clever apology for missing the point of someone else’s e-mail (well, multiple emails over multiple days).

——-

“Roger.”  

This is an affirmation I get of most any statement I make in Skype to one particular guy I chat with all the time.  I guess in this case, my Chinese counterpart is not using English incorrectly at all.  He is just using it in a way no one else uses it anymore, and hasn’t really in fifty-some years.  I only know this because I decided to google it, though.  I knew “Roger” was a term that meant you understood what someone had said, and it had some association with pilots in the military, so I googled “roger as an affirmative statement.”  Turns out it comes from a radio alphabet (A = Alpha, B = Bravo, C = Charlie, etc.) that was the official alphabet of the US Navy until 1954.  One day I will ask where he picked up this statement.

——-

“need go to sleep…pain…headache”

Again, a simple Skype chat.  This time with someone who was trying to explain why he couldn’t answer my question.

——-

On the slightly serious side of this subject, I think I like seeing and hearing these mangled statements because I like language, and warped as these things seem, they give me an opportunity to look at language differently – to consider how it is entirely possible to get your point across in ways that aren’t supposed to work.  Add to that the sort of puzzle-solving aspect of translating the translation and it ‘s a perfect fit for me.  As a kid I loved to watch Jeopardy and I solved logic puzzles for fun all the time, so I guess it’s no surprise I take so much joy in capturing these little tidbits.

More on language and cultural difference

Posted by

0

Last week I shared a sentence that I’d read in an email at work from one of our Chinese team members.  The sentence was : “Sorry about my misunderstand cause this idea so delay.”   A group of us in the US were discussing the idea referred to in the previous sentence.  One of our US architects had been attempting to explain a new approach to calculating whether changes had been made to some objects in a database to the Chinese DBA.  Our goal was to improve performance of the system – if the calculations can be done faster, the user doesn’t have to wait so long staring at a web page with a little gadget that says, “Processing…” that they want to shoot themselves.  In our lunchtime discussion, the US architect explained how difficult it was to get his point across to the Chinese DBA. He said, “Until it make sense to his head, three days he argued on this!”

This stuff just fascinates me.  We’re all trying to use English to communicate, which is clearly harder on some than others, but we’re so far apart sometimes.  I can’t imagine being in the shoes of some of our Chinese team members that know little to no English.  My personal counterpart speaks English well, for the most part, so we have few challenges directly related to language.  The challenges I experience are more around my learning about the cultural norms that matter to them in communication.  A new person that joined our team in the US, though, was describing a recent technical conference call he had with the US Architect and some of the China team.  The goal of the call was for the Chinese team to do a code walk-through with our US Architect and our new DBA.  On the call, the US Architect was the one that was largely explaining what the code did, which really confused the new DBA.  He stopped at one point, and asked the US Architect – “Shouldn’t the guy in China be telling us what the code does?  Why are you doing it?  I thought we needed this call because you didn’t know the code that well.”  What was happening was our US Architect was speaking to the Chinese team – one of them could understand spoken English fairly well, and he was translating for the rest of the group, then responding back to our Architect, who probably had to do some translation of his own before he could regurgitate it for the new US DBA.

I don’t necessarily have a point in recounting all this – but the subject itself is getting interesting enough that I almost feel like starting a separate blog that just talks about these issues.  I really like the juxtaposition of practical challenges and humor that comes with this stuff!

The China team is coming online right now, as this is their Monday morning.  I had sent a bunch of emails on Friday, and I’m starting to get responses to them now.  My counterpart over there just replied to an email I sent him telling him that something we wanted them to do today was cancelled.  He replied, “Roger.”  I wonder where he picked up that term.

Copycat communication

Posted by

0

I grew up in Wisconsin, where accents are thick and colloquialisms abound.  Where else do you drink from a bubbler?  For years, I went “down by” places, not “to” places.  Grilling was “frying out,” and I didn’t even hear it when people ended their sentences with, ” and so?”  It’s not quite as severe as Fargo, but it’s not far off, either.  I called a boat something more like “bow-ut” and shoes “shoo-uhs.”  Native Wisconsinites speak these words a bit faster than you probably just read them, but there is a slight hint of an extra syllable thrown in there, and it happens all the time.  I’m not sure exactly how I shed my accent, but I did, some years ago.  Most people can’t detect it, unless I’m really, really tired, or have had a lot too much to drink, and even then I only slip now and then.

I am, however, easily influenced by the speech of others.  I went to visit a friend in Oklahoma when I was around 12 or 13.  I stayed for a week and came home with a drawl.  I pick up terms other people use, most of the time oblivious to it until it’s too late and I sound like I’m copying them all the time.  What has surprised me lately, though, is how I’m being influenced by the people I work with.  And not in the way I might have suspected, adopting such words my boss uses, like “cycles” and “prosecute” which I’ve written about already.

First, let me say very clearly, I am not being critical or judgmental of the way anyone I work with speaks or doesn’t speak.  It simply is what it is, and it rubs off on me.  I work with more foreign people than native English speakers, especially if you count the hundred employees we have in China.  What’s crazy is that broken English is rubbing off on me.  It’s really hard to comprehend that I would just toss out all the grammar and vocabulary I’ve built in years of speaking and reading and writing, but I’m finding myself slipping into broken English in both speech and email.  It’s kind of nuts!

I catch myself writing things like, “Can you have team work on this today night?” or “Please have a look on this.”  So far, I’m catching and correcting these crazy sentences that are only crazy because English is my first language.  One guy whose English is fine still uses odd phrases now and then.  Instead of saying something happened a long time ago, he says “Remember long back when we talked about that?”  I have used the words “long back” in a conversation with him.  It could be worse.  An email I was copied on tonight had this sentence in it:  “Sorry about my misunderstand cause this idea so delay.”

In all seriousness, though, it is a real challenge to communicate effectively in my organization.  It’s not a challenge I am upset about – it’s a challenge I sincerely think is a good one for me.  I’ve studied diversity and the issues faced in global business – the communication challenges that not only have to do with language barriers, but significant cultural difference, and I am absolutely getting the biggest dose of both of those issues that I’ve ever gotten.  I’m determined to succeed in communicating with everyone, though, and I’m sincerely interested in understanding the cultural differences we all face.  Maybe that’s why I’m so easily influenced by the speech and writing – maybe I’m subconsciously trying to meet them on the terms I hear from them.  Whatever the cause, I will keep you posted on how my language continues to evolve, or devolve, as the case may be.