Newsgroup: it.lavoro.informatica
Titolo: The computer guy

Il sito da cui l'ho preso e` down, quindi lo incollo qui:
-----------------------------------------------------------------------
10 Reasons Why It Doesn’t Pay To Be “The Computer G
---------------------------------------------------
I only met my brother's ex-girlfriend's family once - the year they
invited our family over to share Thanksgiving dinner. Since we were
basically a group of strangers looking to make a good first impression,
the table conversation was nothing more than friendly idle chitchat.
When I asked our hostess for more mashed potatoes, she took the
opportunity to ask me about myself while dishing out my second helping -
"So Shaun, what do you do for a living?"
Hesitantly, I responded: "I work in computer support."
The transition to silence was immediate. All eyes suddenly turned to me,
raised eyebrows all around. If you hadn't heard my response, judging
from everyone's reaction you might think I said something outrageous
like I was a male stripper or a gynecologist - but I knew the awkward
silence would soon be broken by an overwhelming outpouring of computer
questions.
"Oh wow, a computer guy!" - "So you know how to remove spyware and
viruses and stuff, right?" - "Our family computer is really slow, I
think it has a virus." - "Do you have a business card, or can I get your
number?"
I politely and patiently answered their questions, hoping that we'd
exhaust the subject in a matter of minutes and then move on to something
else. As it would turn out, my hopeful prediction was very wrong - the
gentleman sitting next to me scooted his seat closer to me to begin an
interrogation.
This man I was meeting for the first time must've truly believed that I
was going to help him with his problem at that very moment. It didn't
matter how uninterested I looked or sounded, he was convinced that I
must know the answer he's looking for and he was determined he would get
it.
Situations like this one were common for me. I've had eavesdropping
strangers approach me with questions about their computer while I was
eating in a restaurant. I've had oblivious coworkers step in front of me
in a buffet line to tell me about their computer problems while I was
serving myself food. I've had neighbors who spotted me from their window
rush outside to coax me into working on their home computer while I was
walking to the corner market. My knack for solving people's computer
problems had become so well-known among my neighborhood that these
circumstances were near impossible to avoid.
You might be thinking, "So why complain? If your help is in high demand,
why not embrace your talents and charge people for your time?"
I tried to for seven years. I've worked in the computer industry in
various ways - help desk support, web design, consulting and sales,
field technician, freelance computer specialist, and whatever other
fancy name you want to give "the computer guy."
I stopped enjoying it. There were certainly times when I enjoyed myself,
but most of those times were when my computer talents were still
developing. Once I stopped learning new things on the job, I would
become fidgety and want to move on to something else.
From my career-hopping experiences in the computer industry, I've become
acquainted with the Top Ten Reasons it doesn't pay to be the computer
guy:
Reason #10 - Most Of Your Accomplishments Are Invisible
The computer guy never hears anyone tell him, "I just want to let you
know … everything is working fine!"
The reality is that people call the computer guy when something is
wrong.
As a computer guy, if you work really hard to make everything work the
way that it should, and things work fine, then people believe you don't
do anything. Everything you manage to get working correctly or do
perfectly will forever remain unnoticed by computer users. They'll only
ever notice that you do anything when something isn't working correctly,
and you are called upon to fix it.
Reason #9 - Every Conversation You Have Is Roughly The Same
When the computer guy dares to mention what he does for a living, the
typical response is, "I have a question about my home computer…"
Or when the computer guy first hears about a widespread problem within
the computer network he's responsible for, he can barely begin to assess
the problem before a dozen other people call to report the same problem.
Or when the computer guy explains a certain process on a computer to a
user who is incapable of retaining the process, he will inevitably need
to reinstruct the user of this same process - indefinitely.
Reason #8 - You're An Expert Of Bleeding-Edge Technology Products,
Aren't You?
The computer guy often finds himself in situations where someone is
asking him for advice on a pending investment of the technological
variety.
"I heard about (some hardware or software product) that can do
(something desirable) for me. I brought you these
(advertisements/reviews/printouts) because I wanted your recommendation.
Which would you buy?"
Although the inquiring person sincerely trusts the computer guy's
judgment over their own, in almost every instance the real objective of
these meetings is to ensure their own immunity from making a risky
purchase.
If it turns out to be a bad investment, and they cannot get (the
hardware or software product) to do (anything desirable), then you will
be their personal scapegoat - "But honey, the computer guy said I should
buy it!"
Reason #7 - Your Talents Are Forcibly Undervalued
Thanks to the constantly declining price of new computers, the computer
guy cannot charge labor sums without a dispute. If he asks to be paid
what he is worth, he will likely be met with the "why not buy new?"
argument.
That is, desktop computers are always getting smaller, faster, and
cheaper. It's possible to purchase a new desktop computer for under
$400. If the computer guy spends five hours fixing a computer and wants
$100/hour for his time, his customer will be outraged, exclaiming "I
didn't even spend this much to BUY the computer, why should I pay this
much just to FIX it?"
Reason #6 - You're Never Allowed A Moment's Peace
The computer guy is so prone to interruption that he rarely finds an
opportunity to work on his own problems. This is because:
1. Computers never sleep.
2. Computer problems aren't scheduled.
3. Every problem takes time to diagnose.
4. The computer guy can only give one problem his full attention.
5. Each user believes their problem deserves attention now.
Consequently, the computer guy has a 24/7 obligation to keep critical
computer systems running, while simultaneously juggling everyone's
problems. He'll often need to forfeit any opportunities to tend to his
own needs for the sake of others - because at any moment, of any day, he
can be interrupted by someone who wants to make their problem his
problem.
Reason #5 - People Ask You To Perform Miracles
The computer guy is often mistaken for someone who possesses the
combined skills of an old priest and a young priest. I'll sum this up
easily by example:
"No, I really can't recover any files from your thumb drive, even if you
did find it after it passed through your dog."
Reason #4 - Your Assumed "All-Knowing" Status Sets You Up To Let People
Down
There is no common understanding that there are smaller divisions within
the computer industry, and that the computer guy cannot be an expert in
all areas. What makes things worse, is when the computer guy attempts to
explain this to someone asking for help, the person will often believe
that the computer guy is withholding the desired knowledge to avoid
having to help.
This is somewhat related to the next reason:
Reason #3 - You Possess Unlimited Responsibility
The computer guy is expected to solve problems. It is difficult to
determine the boundaries of that expectation.
Some of the oddest things that I've been asked to do include:
1. Use pirated software to undelete important company files.
2. Create an Intranet, after explaining I didn't know how to.
3. Teach someone how to hide their pornography collection.
Solving problems can range from replacing batteries in a wireless
keyboard to investigating why the entire building loses power at the
same time every morning. Resolutions can necessitate weaving a 50-foot
cable through a drop ceiling, or wriggling under a house on your belly
to add an electrical outlet.
Reasons #4 and #3 boil down to this: no matter how often you want to
play the role of a hero, there will always be circumstances that test
the limits of your ability to be one. It's difficult to judge when
helping someone means doing something immoral, and it's even harder to
admit you are unable to solve someone's problem - and chances are, that
someone will view you as incompetent because you were unable to help
them.
Reason #2 - A Life Of Alienation
People only talk to the computer guy when they need him to fix
something. Also, when the computer guy approaches a user, they'll hop up
out of their chair under the presumption that he's there to fix
something - as if it would never be expected that he only wants to
strike up a conversation.
The fact that the computer guy never gets a moment's peace can also
practically force him to withdraw into solitude. His co-workers don't
understand that he doesn't want to hear about their computer problems
during his lunch hour - he does that every other hour of the day. That's
why the computer guy eats lunch alone with his door closed, or goes out
to eat every day - not because he's unfriendly, but because he needs to
escape the incessant interruptions.
Reason #1 - You Have No Identity
It's an awful experience when the computer guy shows up at a neighbor's
doorstep with a plate of Christmas cookies, only to have the child who
answered the door call out, "Mom, the computer guy is here!" He begs for
an identity that is not directly associated with computers, but "the
computer guy" label walks ahead of him - it simply cannot be avoided. I
was given a name and I'd love to be addressed by it.
Having read these reasons, you may believe that I'm complaining. It's
true that I was upset with many aspects of my life as the computer guy,
but I'm past the point of complaining.
I took a good hard look at my existence and realized that things were
not likely to change in the line of work I had chosen. Instead of just
complaining, I took action and began making positive changes in my life.
Working in the compur industry isn't for everybody. It wasn't for me.
I've compiled my reasons for putting it behind me and placed them here,
so that anyone who is unsatisfied with their life working in computers
might recognize it's not for them either.
-- 
Salvatore Iovene
http://www.iovene.com/
"A world without hackers would be a world without curiosity and
innovation." - Jon Erickson

10 Reasons Why It Doesn’t Pay To Be “The Computer G
 :-) ... anzi, :-(
Direi che e' una descrizione accurata di come moltissimi non addetti
ai lavori percepiscono il nostro lavoro e quindi si relazionano a noi.
Ai party sono anni che evito di rispondere direttamente alla domanda
"cosa fai ?" proprio per evitare le situazioni descritte nell'articolo
.. a meno che ovviamente ci siano altre persone che lavorano nell'IT
al party :-)
In quel caso almeno ci si puo' dividere il carico delle "solite
domande" :-)
-- 
Legge di Flon
Non c'e' linguaggio in cui sia difficile scrivere cattivi programmi.
FAQ del gruppo : 
http://aledeniz.blogspot.com/2006/11/le-faq-di-itlavoroinformatica.html

 "cosa fai ?"
E cosa rispondi? "Faccio cose, vedo gente..." :^D

E cosa rispondi? "Faccio cose, vedo gente..." :^D
Eeeehhhhhh, tattiche da party, altro che storie :-)
Essere proattivi, mai passivi, quindi evitare fin dall'inizio che
qualcuno ti chieda cosa fai :) ed intavolare discussioni su vari
argomenti, cercando di prevenire la domanda "ma cosa fai ?", almeno
fino a poco prima della fine del party.
Dopo anche se sanno cosa fai, non c'e' tempo per dare retta ai
problemi dei pc casalinghi.
Certo il problema rischia di presentarsi al party successivo se ci
sono le stesse persone, ma anche li' se c'e' qualcuno nuovo da
conoscere puoi riuscire ad eclissarti molto bene.
E poi conto molto sul fatto che a un party difficilmente qualcuno si
ricorda di chi ha conosciuto, a parte i frequentatori abituali, i
quali pero' in genere hanno una confidenza tale per cui sanno di non
farmi domande relative ai pc :-)
Questo per quanto riguarda party "neutri" (es. per qualche festa).
Per quanto riguarda party dove ci sono piu' rappresentanti del nostro
lavoro, sono molto piu' rilassati e si puo' perfino parlare di
tecnologia senza timore di essere timpinati da richieste di
assistenza.
Quello descritto dall'articolo postato da Salvatore e' verissimo ma ho
notato capita solo se c'e' un solo "computer guy".
Se ce ne sono gia' due e' molto piu' difficile che qualcuno ti timpini
con richieste di assistenza.
Quasi che la gente abbia paura di creare dei conflitti tra "computer
guy" :-)
Oppure, molto piu' probabilmente, perche' se ci sono due o piu'
computer guy e qualcuno fa una domanda di assistenza, la discussione
diventa immediatemente tecnica e i vari computer guy discutono tra
loro usando un linguaggio criptico che chi ha fatto la domanda in
genere va via dopo poco senza aver capito assolutamente nulla della
risposta, ma in compenso ottenendo un bel mal di testa.
Quale che sia il motivoi, ho notato appunto che la probabilita' di
essere timpinato e' inversamente proporzionale al numero di computer
guy presenti.
Se sei solo hai il 100% di possibilita' di essere tampinato (se sei
identificato), se si e' in due hai mediamente un 30% di possibilita',
se si e' in 3 probabilmente si va verso il 5% e cosi' via.
Quindi tra le varie tecniche :
- se si e' soli e non si conosce nessuno :
essere proattivi, guidare i discorsi lontano da computer, discutere di
politica, hobby, ecc.
- se si e' soli e si conosce qualcuno che sa di non fare domande :
stringere alleanze con chi si conosce per creare delle vie di fuga in
caso di essere scoperti.
- se si e' soli e si conosce qualcuno che fa domande :
Questa e' una situazione molto pericolosa :-)
Cercare di stare alla larga da tale personaggio, rifacendosi alla
prima tattica.
Quindi attaccare bottone con altre persone, tenendo d'occhio chi vi
conosce.
- se c'e' qualcun altro professionista IT :
rilassarsi e se qualcuno fa domande, coinvolgere anche altri
"colleghi".
In tempo zero nessuno osera' piu' domandare nulla per paura di
ricevere tonnellate di discussioni in gergo
Chissa', magari salvo qualcuno :-)
Ciao
	Steve


 risposta, ma in compenso ottenendo un bel mal di testa.
Manfatti :^D
Se la butti subito sul tecnichese è facile troncarla sul nascere...
una cosa è se rispondi "lavoro coi compiuter" un'altra è se rispondi
"gestisco un claster di databeis ridondati su architettura a griglia
per una società finanziaria", ci sono buone probabillità che capiscano
solo l'ultima parola... al che ti chiederanno un consiglio per un
fondo pensione :^D
Che se guardi bene il problema vale anche per gli altri... per i
medici, per esempio: ma assistito alla solita scenetta "Ah, sei un
medico? Senti, c'ho un doloretto qui..."
Bye!

 "cosa fai ?" 
Vedi, Stefano, la risposta che do io: "mi occupo di informatica" è
quella che negli anni mi ha dato meno rogne. L'interlocutore rimane
interdetto, perché comunque vede l'informatica come una cosa immensa di
cui tendenzialmente capisce poco; non solo, ma da a me amplissima
libertà di movimento: esempio, "avrei un problema col computer", "mi
dispiace, io mi occupo di sviluppo applicativi", detto col tono fra il
compassionevole e l'altero (sottointende velatamente: "che vuoi che
glie ne freghi, a uno capace di fare programmi, cosa ha il tuo
miserabile computer?"). :-D
-- 
Ciao!
Luca

 Chissa', magari salvo qualcuno :-)
Si, però per spiegare il tuo pensiero hai praticamente fatto un flow-
chart, poi non ti dimenticare se ti danno del computer-guy! :-)
m.

chart, poi non ti dimenticare se ti danno del computer-guy! :-)
Ma il punto e' che io SONO un computer guy :-) e qui un flow chart ci
puo' anche stare bene no ?
Siamo "in tra di noi" :-)


 Eeeehhhhhh, tattiche da party, altro che storie :-)
Si` ma facciamo che nonostante tutte le precauzioni, all'improvviso
sbuca dal nulla uno che ti chiede "Tu che lavoro fai?".
Messo alle strette con una domanda diretta, tu cosa rispondi?


quella che negli anni mi ha dato meno rogne. 
Magari a Varese.
A Little Rock e' diverso :-)
Primo perche' la parola informatica non esiste da queste parti, la
dizione equivalente usata e' "computer science" che e' anche peggio :)
Secondo perche' in genere mi invitano a party dove bazzicano
professionisti che non si lasciano intimorire dai paroloni ma che
comunque hanno PC da mettere a posto :-)
Quindi come vedi ho dovuto sviluppare altre tecniche.
Ciao
	Steve


 Messo alle strette con una domanda diretta, tu cosa rispondi?
come fosse antani
-- 
FabMind

Messo alle strette con una domanda diretta, tu cosa rispondi?
Lo sviluppatore di programmi per elaborazione dati non su piattaforme
standard.
In italiano :-)


 comunque hanno PC da mettere a posto :-)
Bei professionisti, se non si arrangiano... :D
-- 
Ciao!
Luca

Bei professionisti, se non si arrangiano... :D
Non professionisti IT :-)


 standard.
...You bloody bastard... :-))))
I just try to stay away from parties altogether.
E se me lo chiedono... "Software for Systems based on microelectronics
circuitry"
...che vuol dire "Computer Guy", ma un'americano medio non lo capira'
mai... :-)
Piero

mai... :-)
Mmmmm temo invece lo capiscano :)
Di buono c'e' che esiste "Geek Squad", rilevata qualche mese fa da
BestBuy, per cui almeno possiamo indirizzare chi rompe per una
consulenza, li'.
E a giudicare dalla richiesta di personale per quel business, direi
che ne hanno di lavoro :-)
Ciao
	Steve


> Messo alle strette con una domanda diretta, tu cosa rispondi?
A) Faccia dello smile di messenger corrispondente a " :| " che dura due/tre 
secondi
B) Esclamazione a voce alta : * "EHY GUARDA! UNA SCIMMIA A TRE TESTE!" * 
(cit.) ©
C) Eclissi Ninja Style in mezzo alla folla
;)


Mi hai fatto scendere una lacrimuccia :)
Bei tempi

 10 Reasons Why It Doesn't Pay To Be "The Computer G
Devo dire che a volte concordo con l'autore. Non sempre, ma di quando
in quando capita, ed infatti ho seriamente pensato di andarmi a farmi
1 anno di CPE/GDL (
http://www.lawcabs.ac.uk/cabonline/cpelist.htm
) e
specializzarmi poi in international business law .. yeah, più o meno
ogni volta che mi lascio andare al lato oscuro della forza :))
--
ale
http://ale.riolo.co.uk

 "cosa fai ?"
A volte rispondo "lavoro nell'healthcare", ma poi inziano a dirti "sai, 
ho un dolorino qua, sotto l'ascella....che potrebbe essere?". Allora ho 
camibato tecnica e mi son buttato sul dummy guy: "mah, mi pagano per 
smanettare un po' su una tastiera, ma in realtá non ci capisco mica 
nulla, non so manco come si usa word!". A quel punto diventi 
automaticamente inutile: il tuo interlocutore (che usa abitualmente 
word) si convince che ne sa piú di te e chiude li le domande.
ciao, U.


"io no parla taliano"
m.

 Messo alle strette con una domanda diretta, tu cosa rispondi?
Sarà che sono masochista, ma rispondo "lavoro nella sicurezza
informatica"
e allora giù di domande di antivirus, spyware, router ADSL,
Wireless :-)