Blimey

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Question:

When does your fellow colleague become a "user"?







































Answer:
When s/he cannot delete a file

Seriously, how that person got the job, i have no idea!

A solution was to delete 2 files within the program files dir, everything was written step by step, and all i got was a puzzled look.

I asked the <person> what s/he was waiting for? and <person> said did not know what to do, my reply was... er, delete them two files, and all i got back was a puzzled look , so i gave back. And??? i asked, reply was; i dont know how to delete... FFS! i actually thought <person> was taking the piss! later on the day, i asked <person> to go back to the desktop, and same shi7, <person> was confused!

Geez, for this day on, <person> will not be known to be as a fellow IT Tech (which is what i call my colleagues, and it is what we are), as from this day on, <person> will be known as

USER

 

Awww mrcheeks, I know it is a pain and it was a shock. But you should talk to this person see if this is the field they really want to be in or is it just another job to them. If they really want to be a tech you should take them under your wing and mentor them.

Now, now, before you blow a gasket, just think about it. Weather you like it or not they are there and your going to have deal with them. If you start training them then they will lean their job faster which will not put as a much on your shoulders. You will be building bridges and who know what can happen down the road. Plus it is just the nice thing do. Remember, what goes around comes around.

 

Mitz - i see what your saying, and would "normally" do that regardless whether the person knew what they were doing or not... i stop caring, when they stop, and i spoke to <person> already, and <person> doesn't like to sit in office jobs and cant understand computers, infact cant be bothered to understand them.

if <person> couldn't understand compters, but still was eager to learn, hell, this thread wouldn't exist, and i'll guarantee by the time i finish training <person>, <person> would be exceeding the requirements of his/her role, but of course, <person> doesn't give a monkeys....

my line manager has something lined up for <person> tomorow, the outcome would be very interesting!

 

He won't have to deal with <person> long if <person> can't do the job. Which, from all indications, seems to be the situation.

 

The <person> tag you've been using reminds me of XML so I thought I'd recode your original message just for giggles.

<?xml version="1.0"?>
<!DOCTYPE enduser SYSTEM "/xml-resources/dtds/enduser.dtd">
<enduser>
<question>When does your fellow colleague become a <plonker>user</plonker>?</question>
<answer>When s/he cannot delete a file</answer>
<answerlong>Seriously, how that person got the job, i have no idea! A <solution>solution</solution> was to delete 2 <object>files</object> within the program <object>files</object> dir, everything was <instructions>written step by step</instructions>, and all i got was a puzzled look. I asked the <plonker>user</plonker> what s/he was waiting for? and the <plonker>user</plonker> said <comment>they did not know what to do</comment>, my <response>reply was... er, delete them two files</response>, and all i got back was a <response>puzzled look</response> , so i gave back. <response>And??? i asked</response>, reply was; <response>i dont know how to delete... FFS</response>! i actually thought <plonker>they</plonker> was taking the piss! later on the day, i asked <plonker>the user</plonker> to go back to the desktop, and same shi7, <plonker>the user</plonker> was confused!
</answerlong>
</enduser>

 

We'll soon find out - i'm hoping <user> doesn't stay - im not being spiteful, but the reason i say this, is because,

1- It is for <user> own benefit to find something more interesting
2- The other tech's around will rip <user> apart and <user> would feel that <user> is some sort of *glitch* in the system...

Sweet... just added two tags, which i *think* should be there

 

Trip you bloody geek

 

...sorta like a PEBCAK error, eh?

 

Cheek, you get some reps points because you would if he was interested! That makes you rock in my book. I don't care what wizard says about you.

 

They would if that person happen to be related to someone high up and it is how they got the job in the first place. Or if it is a wanna be tech that just happen to luck into the job. It is easier to just make the best of a situation instead of banging your head against a wall. But since they are not interested, there is no sense in him wasting his time.

 

It is not only waste of time for <user>, it is also a waste of time for
myself
my fellow IT techs
my manager
service centre
the entire company.

domino effect! the more time we spend resolving <users> issues, the less time we spend dealing with <more important> issue and delay in resolving any of our own problems we may have with the most important person out there! ...and thats the customer!

time = money

 

There are ways, and there are ways. MUHAHAHAHAHA!!!

 

You think that's bad...watch this:

This is the contents of a file named "telegram.xml".

<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="ex2_memo.css"?>
<telegram pri="important">
<to>Sarah Bellum</to>
<from>Colonel Timeslip</from>
<subject>Robot-sitting Instructions</subject>
<message>Thanks for watching my robot pal <name>Zonky</name> while I'm away. He needs to be recharged <emphasis>twice a day</emphasis> and if he starts to get cranky, give him a quart of oil. I'll be back soon, after I've tracked down that evil mastermind <villain>Dr. Indigo Riceway</villain>.
</message>
</telegram>

This is the contents of a file named "ex2_memo.css":

telegram {
display: block;
background-color: #FFEBCD;
color: black;
font-family: monospace;
padding: 1em;
}

message {
display: block;
margin: .5em;
padding: .5em;
border: thin solid gray;
background-color: aqua;
}

to:before {
font-size: 1em;
color: black;
padding: 1em;
content: "To: ";
}

from:before {
font-size: 1em;
color: black;
padding: 1em;
content: "From: ";
}

subject:before {
font-size: 1em;
color: black;
padding: 1em;
content: "Subject: ";
}

to, from, subject {
display: block;
color: blue;
font-size: large;
}

emphasis {
font-style: italic;
}

name {
font-weight: bold;
}

villain {
color: red;
font-weight: bold;
}

Paste the contents into a text editor and save each file by the names I've indicated. Make sure both files are in the same folder. Open telegram.xml in a web browser and you'll have a document that looks like the one in my attachment.

I know this is pretty elementary, but it's also kind of cool.

Got the example from the O'Reilly book Learning XML.

 

Okay had a brain fart, it was displaying it in IE6, works fine in FF2.

 

whats a brain fart?

 

Ha haaaa! Ooh, dunno - maybe some special kinda "by product" wizards produce when they conjure....imagine the stench from one of those - pheeeew!!

 

A brain Fart is like having a blond moment.

 

And we all know you have plenty of those.

:runs like a bunny: