The Frustrations of Supporting Users In Remote Offices 129
Esther Schindler writes "You're not alone in your struggle against people who think a shell is something you hold to your ear," writes Carol Pinchefsky. "Other techies are out there supporting users in remote offices, fighting the good fight against computer- and user-related mishaps – or at least tolerating user frustration with a modicum of grace." One example she gives is a tech support person whose systems in Brazil went down — during Carnival: "...We had to wait more than a week for the locals to sober up enough to reconnect the line. In the end, I had to walk a tech (who did not know the system) through the process step by step via an interpreter. Of course, the interpreter was not technical. So it was kind of like explaining to your mom to tell your grandfather (who is hard of hearing) how to do something while she is on the phone and he is across the room from her."
Users in remote offices are the best users! (Score:5, Insightful)
Users in remote offices are the best users! They can email, they can call, and they all get a ticket opened for their issue. But they can't come make a scene in your department (or worse, at your own desk) because "the data pull I asked for last week is clearly out of date, my customer from yesterday isn't listed" etc. I would much rather support users via email, via ticketing, and via phone if necessary, than support them in person.
Re: (Score:3)
Indeed. Moreover, email and/or texting helps surmount miscommunication due to heavy accents and bad phone connections. Often I've ended a puzzling scratchy phone call with "can you send me that request through email?" And then I get the email, oh yeah, that's what he meant.
Re: (Score:1)
Moreover, email and/or texting helps surmount miscommunication due to heavy accents and bad phone connections.
Indeed. [imdb.com]
"Best" users (Score:3)
For your company, remote users are the most expensive to support. It often takes several minutes to try to make the user understand what you want them to do, and to do it PROPERLY, where locally, you could just go to a user's desk and fix the problem in seconds.
When dealing with local users, you get to use *ALL* of your senses to diagnose a problem. Does the computer feel abnormally hot? Does it smell like something burning? Can you see that the little tab on the ethernet cable is broken off?
Re: (Score:2)
For your company, remote users are the most expensive to support. It often takes several minutes to try to make the user understand what you want them to do, and to do it PROPERLY, where locally, you could just go to a user's desk and fix the problem in seconds.
Therein lies a pretty big problem IMHO, even if it takes you a couple minutes the remote user can now deal with the issue themselves (assuming its something that doesn't require co-ordination with us). Also they now have documentation (in the form of e-mail) in the event they forget. If you just walk over to the user's desk they are not going to bother remembering how to fix it themselves they will remember where your desk is the next time.
I acknowledge from a debugging perspective it can be harder but I wo
Re: (Score:1)
Hey, I don't like doing phone support either. Taking a phone call puts you on the spot, with no time to think through your response or prepare an answer. There's no proofreading on a phone call. Which is precisely why some people will always insist on calling, because they know it makes you uncomfortable and assume they can take advantage. It's poor form to say "no," so I learned a long time ago to use the "I'm not sure, but I can find that out for you, I'll shoot you an email" approach. Most folks catch on
Re: (Score:2)
Re:learn Portuguese (Score:4, Insightful)
If you are big enough to have a branch office in Timbuktu then you should be big enough for there to be someone in the home office that speaks whatever they speak there.
Of course this runs counter to the current corporate culture fad of cost cutting and defining success based on quarterly profits and stock results.
Re: (Score:2)
Re: (Score:3)
It would make far more sense for the Brazilian tech to learn English. Many technical docs are available only in English. It is the language of science and technology, and any journal or conference that wants an international audience is conducted in English. It is the language of international business. If the Brazilian tech has any ambition, he is going to have to learn it.
I once spent three weeks in Sao Paulo. I don't speak Portuguese, and only know a little Spanish, but I didn't have much problem.
Re: (Score:2)
Re: (Score:2)
Spanish? Brazil is Porra last I checked.
Look at a map. Portugal and Spain share a 1,214 km border. Portuguese is more similar to standard Spanish than some Spanish "dialects" within Spain. If you speak Spanish in Brazil, people will usually get the gist of what you are trying to say. You are not going to be able to do standup comedy, but it will suffice for simple phrases like "I want that" or "where is the toilet". Lots of Brazilians are familiar with Spanish because they watch Mexican soap operas.
Re: learn Portuguese (Score:2)
Re: (Score:2)
Re: (Score:2)
I was going to post that! Seriously if we now have "Dev-Ops" why not "Dev-Interps". This is the age of flexibility and doing more with less. I always feel embarrased when I work with someone overseas and I do not know their language, not even please or thank you. They took the trouble to learn my language, I should reciprocate.
Show Users some love! (Score:5, Insightful)
IT needs to let go of PEBKAC and ID-10-T errors. Your users have difficult jobs and they probably don't want to deal with you any more than you want to deal with them. They probably aren't "bothering" you for fun. If they are, you're doing your job well.
Yes, they can be dense. But guess what -- they are human and so are you! They make mistakes. So do you!
I enjoy The IT Crowd and BOFH, but those are fantasies and should remain such.
There are many reasons to show appreciation for the work your coworkers do. The most important is that without them, you may be lucky enough to find yourself in their shoes.
Re: (Score:2)
Re: (Score:2)
That doesnt mean your users are idiots, and if thats your starting point, you're probably creating more of your own problems than anyone else.
Re: Show Users some love! (Score:1)
With closed source there is often no other solution available, though. I pity those poor bastards that have to work around problems caused by software they can't do anything about...
Re: (Score:1)
Actually many times its just some sort of conflict. If a reboot causes the issue to go away and it doesn't reoccur then I don't worry about it. If it happens again then it is an issue that needs to be properly diaged.
Hell, I often stay on the phone with my user until I know he/she is back up and running. I then instruct them to shoot me an email if it reoccurs. Id say about three quarters of the time it does not reoccur. I am guessing you have never actually worked a help desk for a windows shop have y
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
Maybe you're both correct to some extent. Rebooting certainly doesn't solve all problems. But the software architecture used in Windows/Unix does have the unfortunate characteristic that it sometimes manages to transition into states that no one anticipated and that do undesirable things. Rebooting restores a more desirable state. At least for a while.
There is also a problem that few modern PCs use memory capable of detecting memory errors Thus it's possible for values defining system state to change s
Re: (Score:2, Interesting)
Sometimes it does. For example, Windows Servers will occasionally just lose the fact that they have file locks on certain files. They will function, but can't be accessed via the UI.
Only way to fix it is to reboot the server. Trust me, I thought it was insane at first, coming from a Linux/Unix background. There had to be something... nope. If it's not in the main UI, it won't show in any other locations, however, it'll function just fine to lock that file. Rebooting saves a hell of a lot of time. Even if I
Re:Show Users some love! (Score:5, Insightful)
Re: (Score:2)
They could do that, but their whiny lazy asses would want the company to pay for the training. Paying for training literally makes you Hitler.
Re:Show Users some love! (Score:5, Insightful)
Sorry, but no. Simple as that. No. The problem is that people are to use a tool and cannot be assed to learn how to use it. And don't turn around and blame corporate by "but they make me". Then learn to do your goddamn job or GTFO of it, you're wasting valuable oxygen someone else could use productively.
I've spent a good deal of my youth in support jobs. They work well as part time during your university years, and that you're treated like garbage by the cheese-for-brains idiots doesn't really help to endear them to you either. I've seen them all. From the lady who flat out refuses to remember passwords and needs a reset twice a day (one in the morning, one when she returns from lunch) to the gentleman who calls every other day to be walked step by step through the same problem who yells obscenities at you to compensate for his own idiocy that apparently keeps him from writing down those steps.
No. Sorry. My patience with users has expired long, long ago. Learn to use your tools or vacate the position for someone willing and able to do so.
Re: (Score:2)
DEAL!
You have NO idea what uphill battle it is to convince certain people in upper management that they do not need admin privileges on their PC. I know, I know, what kinda audacity that I wanna give that tech peon more "power" than his excellency the CfuckmeO and his secretary.
Because he doesn't fuck your machine up for good by downloading every single friggin' shit angry-birds-knockoff game, that's why!
I swear, one of those meetings I'm gonna flip.
Re: (Score:2)
There was one place I contracted at. As a developer, I was allowed administrator privileges. First, though, I had to read and sign a document that said that I understood that tech support was limited, and that if a tech worked on my computer for more than half an hour he or she would wipe and re-image.
Au contraire! (Score:5, Insightful)
Re: (Score:3)
What a useless and whinging article! You find remote support frustrating? Some of us recall the days before remote support was an option, having to hop in a car and drive somewhere every time a problem occurred. Remote support is a f*cking godsend. Don't work in support if you can't handle a bit of frustration.
I remember those days. We had to strip RG58 cable with our teeth and punch down wires with our foreheads while holding a 50 pound roll of Cat 3 in each hand. Kids today, they don't know how good they got it.
Now get off my BBS.
I think the author's point was, in today's world remote support has a few new wrinkles, like distances you couldn't drive in a reasonable amount of time, different cultures, language and technology barriers. Some of us got an early start in this area (I worked for a Japanese-based c
Re: (Score:1)
They're still whiners. Try writing code to support multiple languages simultaneously on heterogenous environments with users attempting to look at the same data. Back around Y2K. And then supports those users.
For some reason, kids today think they have all these new exciting special problems and that they're in a eureka moment. That wasn't even true when I encountered those issues more than a decade earlier. I'm pretty sure the initial international connections for what became the internet were not even th
Re: (Score:1)
Re: (Score:1)
Au contraire - INDEED (Score:5, Insightful)
What a useless and whinging article! You find remote support frustrating?
It's more than that. these "support" people find their "users" objectionable - the people for whom they serve and the reason they have a job.
Many if not most people use computers for a varying scale of applications. Most of these people are not "computer professionals". If you are in "support", your job is to "support" these people. If you can't handle that, it's time for a new job.
Re: (Score:3)
Stupid customer said what?
Sure, it's biting the hand that feeds you, but the us versus them theme is practically genetic.
Re: (Score:2)
Re: (Score:2)
I dont 'serve' you, we are peers.
If you are in "support" than yes, you *do* serve me. We may be "peers", but I AM YOUR CUSTOMER.
If you can't handle that, get out of "support".
Re: (Score:2)
Re: (Score:2)
Did I specify "desktop"? No I did not. I'm still the customer, asshole, get over yourself.
Re: (Score:2)
You sound like a real treat to work with. Issues like yours mysteriously found their way to the absolute bottom of my list, because when you treat people whose assistance you need to do your job like shit, they react accordingly. Tech support is not your personal abuse sponge. And you don't need to be a fucking "computer professional" to remember an 8-character password, or to know that you
Re: (Score:3)
And then IT wonders why people circumvent their policies. And then semi-tech-savvy people implement workarounds outside of IT and it all goes well until it doesn't.
And when it doesn't, the crap hits the fan quickly because most likely it's some hacked-together system some manager set up years ago that ended up as a production critical system. That no one remembers, or even knows where it's at until some move later or IT comes ar
Re: Au contraire - INDEED (Score:2)
I counted 5 terminable offenses at most sane companies in this comment. IT policies are not there to impede you or just annoy you; they are there because assholes like you think you know IT's job better than they do. If you are not getting the answers or support you need from IT, or you don't like a decision they make, the answer is not to break policy and work around it. The answer is to escalate the problem up the chain and lay out very clearly and patiently what you are asking for and why it's importa
Re: (Score:3)
What I found really smooth was to use create a mix of internal and external contracted support. Troublesome users are passed off to the external support and good users are done internally. The troublesome types want to use some else to prove how bad you are and they are happy until they start to realise how long external support takes and management gets the bill for that detailed external support of them. Everyone else learns to be a lot happier with the quick, direct, personal support and of course in ov
Re: (Score:1)
A couple of years ago someone on slashdot posted an interesting system for dealing with obnoxious assholes. If I recall correctly they were doing support as external contractors.
What they did was that they always wrote down who it was that needed support and how much time was spent on it, and then they put together a high-score list every month.
This had many benefits. First of all their customer got to see that they weren't really expensive, it was just that some people in the office needed a lot of support
Re: (Score:2)
Re: (Score:2)
You're lying. Everyone knows private industry is so much more efficient and responsive than the government so you're just making up this shit.
Private industry would NEVER treat their customers in the manner you described. They would bend over backwards, expending all needed time, effort and money to make sure your problem is resolved quickly and efficiently.
For those who don't grasp sarcasm, this was it. I work for a governm
Patience is the key (Score:5, Insightful)
For me it's important to keep in mind, I get paid the same regardless, so it's not worth getting twisted up about it. Communicate slowly and clearly, use simple instructions, ask politely for feedback (what do you see on your screen now?) and you'll eventually get there. Unless your remote user is trying to defuse a bomb, how long this takes probably doesn't matter much in the long run. So relax.
Once, at 3AM or so, modem out of commission, no way to log in, I talked an operator through editing a backup script that another admin had broken. (Made a change, didn't test it.) It took a long time, but we got it done and I didn't have to drive in. In his favor, the operator was excellent at following instructions and telling me what exactly he was seeing on the screen.
Re:Patience is the key (Score:5, Insightful)
As someone fairly green on the helpdesk (just hit the 1 year mark), I must say that I appreciate ten times more a user who follows instructions and describes what's on their screen, than users who claim to be tech savvy, broke what they were working on, and can't seem to fix it themselves.
What I really hate are those users who never learned how to use their computer. They know how to operate one or two programs on the computer, but they always say "I'm not a computer person", and use that as an excuse for never learning the difference between the mouse, the monitor and the tower. The kinds of users who can't take instructions because they're unwilling to focus their eyes in unfamiliar territory on the the screen.
I'm fine with ignorance, ignorance can be fixed, and ignorance is honest. What I can't stand is when people call in asking for help, but refusing to say what they need help with, then when you pry it out of them, they refuse to follow the instructions you give them. Those are the worst users.
So yeah. Compassion is great. I do my level best every day to put myself in the users shoes, because I understand how stressful it is when your tools fail you. But there is certainly a point where the patience runs out, because someone who is asking for help (often demanding help) is not willing to be helped once they have my attention.
Re: (Score:2)
My favourite ones are ones that go along the lines of.
"My email is all gobbledy gook, can you fix it"
"Ok, forward the email to it@blah.com and I will have a look"
"How do I forward an email?"
"Push the button that says forward and has an arrow pointing right. It is on the right hand side of your email about half way up"
"No it's not"
"Ok. Can you see a menu up the top marked message"
"No - where would that be"
"If you start at the top left corner you will see File, then Edit, View, and finally Message"
"Oooo the
Re: (Score:3)
A year? You're a veteran. Maybe at the pinnacle of your productivity.
Past the 1.5 years mark, everyone just either loses any kind of motivation or starts doing happy pills to stomach the crap.
Re: (Score:2)
I remember a job where I had to take acid suppressors (the kind you take for acid reflux) during the workday just to get through the day. I'm really glad I don't work there anymore. Some places are just poison. The only solution is to be somewhere else.
But in that case, the user community had built up a remarkable hostility towards IT (somewhat deserved) over a number of years. Not something you could easily solve in a few months.
Re: (Score:2)
Re:Patience is the key (Score:5, Insightful)
For me it's important to keep in mind, I get paid the same regardless, so it's not worth getting twisted up about it. Communicate slowly and clearly, use simple instructions, ask politely for feedback (what do you see on your screen now?) and you'll eventually get there. Unless your remote user is trying to defuse a bomb, how long this takes probably doesn't matter much in the long run. So relax.
Once, at 3AM or so, modem out of commission, no way to log in, I talked an operator through editing a backup script that another admin had broken. (Made a change, didn't test it.) It took a long time, but we got it done and I didn't have to drive in. In his favor, the operator was excellent at following instructions and telling me what exactly he was seeing on the screen.
In some ways I got lucky. One of my first jobs was supporting point-of-sale systems and pump controllers at 100 gas stations, about 30% were 24-hour. There is nothing like walking a minimum wage cashier through resetting a pump controller and being woken up at 3:00am in the morning as trucks are lining up and they can't pump gas... If you have the patience to do that, you can support just about anything...
It taught me how to be patient, professional, to ask all kinds of questions, and to pay attention to any and all details that are provided. It also taught me how to put myself in the place of the person on the other end of the phone and how to calm them down.
Re: (Score:2)
> The other thing I learned is that rebooting machines is for whimps who don't want to know what is really wrong... we couldn't reboot certain machines, it'd take 20 minutes to get the store back up if we did... so we'd troubleshoot the actual software configuration and restart processes that were hung instead of taking the entire system down for one failed service... Of course that is an ideology that doesn't permeate the world of support.... and quality support is rare because most people in support se
Re: (Score:3)
The problem is the person complaining isn't very good at his job or prepared for situations that should be expected.
He seems to think getting something done during Carnival is supposed to be easier than getting anything done in France during August or over Christmas weekend in Spain or the USA.
Re: (Score:2)
Re: (Score:2)
So do mine, but I'm prepared for providing them service during holidays by having SLAs across my vendors that ensure they will be supported during those holidays.
I also test on random occasions my vendors ability to support these times by intentionally 'breaking' something or at least simulating a break.
What I don't do is act surprised that Joe's no name 'data center in my closet at home' isn't around to support my servers in his closet because its that time of year when he goes and does something else ...
Re: (Score:2)
heldesk people writing articles wow! (Score:3)
Re: (Score:2)
If only someone invented something that allowed me to see what's on the person's screen...
Re: (Score:2)
"But ... but ... but then the techs could SPY ON ME!!!!!1elevenexclamationmark!"
Yeah. Because they got nothing better to do than watch you play Angry Birds. Why does everyone think he's interesting once his title starts with a C?
Re: (Score:1)
I think a better analogy is to say it's like trying to work with someone that speaks another language, when the interpreter is not a technical person.
That's not an analogy. That's a summary.
Comment removed (Score:3)
Re: (Score:2)
The right phrase is "Help me help you". The comma changes the meaning to something irrelevant to this discussion.
I never thought I'd be one of these posters (Score:2)
but consider yourself lucky someone wants or needs your help. This industry and capitalism's desire for endless efficiency and profit means a fair few of us reading your post are sitting at home without a job at all.
I'd gladly sit on the phone through a translator to fix something, infact I'd be inclined to think you're probably at a medium sized business or smaller if you're dealing with something like that, so it's probably within your power to do some pretty interesting and dare I say "cowboy-ish" stuff
Re:I never thought I'd be one of these posters (Score:4, Funny)
I'd gladly sit on the phone
You're doing it wrong.
See, this is the kind of problem that makes it difficult for tech support to help you.
Re: (Score:2)
If you read his post, I got the impression the link was down, remote access wasn't a viable option. If that means an administrator needs to talk someone through unplugging / re-plugging something or confirming a diagnostics LED, so be it, they're employed regardless.
Re: (Score:2)
***woooooosh
If you're sitting on the phone, you probably can't hear whats being said or talk to the person on the other end.
It was a joke.
Re: (Score:2)
I believe he's suggesting that sitting on a chair and talking on the phone is more effective than the other way around.
Re: (Score:2)
Oh wait, I just got it........sheeeit.
this (Score:2)
If you work in support, you're going to eventually end up in a situation where there is a server that needs to be addressed, but there is no phone in that room, and so you end up with this same sort of scenario (talking through someone). You should probably just express your frustrations wit
Re: (Score:2)
Personally, I'm surprised if someone in IT even knows what a shell is. As an end user I'm frustrated by being told to turn it off and back on again, or being transferred through three departments until they find the one and only IT employee who actually understands computers.
Remote offices are great. It means not everyone has to crowd into the main headquarters, it also means that the IT people don't have to all crowd together too. What's good for all workers is good for IT workers, so it's a good thing
It's easier now (Score:1)
what? (Score:5, Insightful)
One example she gives is a tech support person whose systems in Brazil went down — during Carnival: "...We had to wait more than a week for the locals to sober up enough to reconnect the line. In the end, I had to walk a tech (who did not know the system) through the process step by step via an interpreter. Of course, the interpreter was not technical. So it was kind of like explaining to your mom to tell your grandfather (who is hard of hearing) how to do something while she is on the phone and he is across the room from her."
Ok, that's just... I don't even know what it is... ethnocentric? It's stupid... not everyone in Brazil gets wasted during carnival. Businesses still run, things still work. If you had a line go down for a week without repair, that wasn't your remote users fault. That was your businesses fault for having a shit contract. Where we work we have tens of thousands of data and voice connections in every remote area you can imagine and there's no way something could go out for a week without a very good excuse like the building burnt down, or there was a flood. Even then we'd find a way around the problem temporarily. It's been more than one time I've kept a company in business with Cat5 strung through some trees.
And the language thing? Give me an Fing break. I had to support a doctor in India that did not speak english, so I made a wild guess, hit the directory of the hospital and looked for an American sounding name. Sure enough it was an American and he was nice, helped translate. I sent him detailed instructions and he helped walk the other doctor through it. That's our Job If I'm a window washer, I'm not going to complain when I come across a dirty one.
The website is down (Score:2)
https://www.youtube.com/watch?... [youtube.com]
.
Re: (Score:2, Insightful)
You are there to serve them (Score:3)
Calmly try your best for 40 hours/week or whatever you agreed to. Explain limitations and possible solutions, like user training and shifting parts of infrastructure to where you are in a better position to maintain it. Then set the limits, but don't be rude. You don't pay the company's bills, your users do.
Your company's fault actually (Score:4, Insightful)
... for not having contacted a local tech contractor with some english speaking skills that could help. Someone that comes in a couple hours now and then to solve any issues.
Remote tech support is all fine and dandy, but sometimes you do need (technically literate) hands and eyes on the ground. I've taken care of servers on a different continent - 99% of the time I just ssh-ed in. The 1% I've had someone local - and technical! - drive in with a laptop and help.
Re: (Score:2)
Correct and as a brazilian working in the IT field I can attest that those times of the year (carnaval, christmas, mothers day) the techies are usually doing overtime to assure your shit does not break down. Carnaval is like any other holiday either you are on call receiving overtime or you are not and the next day after the holiday is over is back to business as usual.
BT, DT... (Score:2)
Many, many years ago (1986 or so?) we had a branch oil exploration office in Iran, surveying new oil fields close to the border with Iraq.
Getting any kind of computer gear in or or out of the country was "difficult", and the best possible data connection was an extremely expensive 256 kbit/s satellite line.
One day I was told to help, over a bad phone line, a guy down in Teheran whose PcDos computer had crashed:
I was able to figure out that his crash had modified/overwritten the Boot Block on his hard drive,
Re: (Score:2)
How about FDISK
Re: (Score:2)
You are right, if it had been a pure Dos problem those would have worked, this probably means that the partition table was the victim, but I obviously don't remember all the details now. :-(
I see it differently... (Score:4, Insightful)
Re: (Score:2)
She works with a whole system in Brazil via an non technical interpreter? Did it ever occur to her to learn Portuguese language?
Sure that's practical, along with learning all the languages of all the offices one has to support globally.
Re: (Score:2)
Many people around the world speak English at different levels. Sometimes it is just Globish or an Airport English. But Brazil is an enormous country where people do speak Portuguese. No way around it.
Re: (Score:2)
Then at least she could avoid blaming a carnival, and concentrate more on her linguistic skills. Or hiring Portuguese speaking engineers instead of non technical interpreters to run a computer system in Brazil.
Many people around the world speak English at different levels. Sometimes it is just Globish or an Airport English. But Brazil is an enormous country where people do speak Portuguese. No way around it.
Or maybe the people in Brazil were out partying instead of working. Were you there somehow and you have information that lets you assume that the author is actually incorrect in their statement?
Anyway. I support networks in many countries around the world including Brazil and it is just not realistic to learn another language to be able to support them.
Perhaps if it were my primary or only customer base, maybe. But you have no idea that this is the case with the author.
Re: (Score:2)
... it is just not realistic to learn another language to be able to support them ...
It is quite common in Europe to speak two or three languages fluently. If there are 2 - 3 engineers who speak 2 - 3 languages fluently then most of the major languages are covered.
By the way, it is often just a stereotype that all people are drunk here or there. Brazil economy grew 2.5% in 2013, it is certainly achieved by hard working people.
Re: (Score:2)
... it is just not realistic to learn another language to be able to support them ...
It is quite common in Europe to speak two or three languages fluently. If there are 2 - 3 engineers who speak 2 - 3 languages fluently then most of the major languages are covered.
By the way, it is often just a stereotype that all people are drunk here or there. Brazil economy grew 2.5% in 2013, it is certainly achieved by hard working people.
I live in Europe and I speak two languages fluently but I still believe it's completely impractical to learn all the languages when supporting a global deployment of systems or network devices. If you had to interface with users, then I would agree - but that isn't the case here.
Anyway, if you read the article the problems they encountered had nothing to do with language:
"Unfortunately, this was during Carnival. The local phone company did not answer, and the local employees did not answer their mobile pho
Re: (Score:1)
Not being able to communicate with people you are hired to support is most certainly your problem. If she had no viable method to do the job, why did she accept it? That makes her pretty stupid from the start.
If you want to talk about practical, it started long before someone mentioned learning the language.
Do you think its okay for someone to claim they are a Java developer without knowing a single bit of Java?
Re: (Score:2)
Not being able to communicate with people you are hired to support is most certainly your problem. If she had no viable method to do the job, why did she accept it? That makes her pretty stupid from the start.
If you want to talk about practical, it started long before someone mentioned learning the language.
Do you think its okay for someone to claim they are a Java developer without knowing a single bit of Java?
What in the world are you talking about? Did you even bother to read the article?
Let me help you:
"Unfortunately, this was during Carnival. The local phone company did not answer, and the local employees did not answer their mobile phones. After two days we got someone from the phone company on the line — and they were too drunk to understand us."
Where in that is there a language problem?
What is support? (Score:1)
This is the NEW economy, pal. There's no support. But no one cares either because all executives are compensated according to how LITTLE they spend even if, especially if, the job done is shit.
Did it a long time ago ... (Score:2)
I had to deal with a remote customer whose person on site does not speak English, by getting him to enter UNIX shell commands. His native language (and mine) was Arabic.
What I did was to tell him what Arabic key to press so that the English equivalent would be the one sent to the shell.
We were lucky that his Arabic keyboard layout was the same as mine. That was not a given in those days (Late 80s, early 90s), but we lucked out.
He was describing to me the output in English (vertical bar, vertical bar with a
Support peeps who bitch about users ... (Score:2)
... should STFU.
Professionals walk a fine line between dealing with distraught users and causing World War III.
Doing your job in a way where you get invited to lunch with your other coworkers is the right way to do things.
People who call users "idiots" are "jerks".
So it is written, so let it be done.
Solved! (Score:1)
I got so tired of supporting remote offices that I outsourced that task to a remote office.