computer people

[Code]

anabolic,

You are right and wrong. Some people are mechanics, as you say. These are the hardware people. Most only get A+ certified and call it a day. There is a whole other world out there. And yes, you do need atleast a 4 year degree for some positions.

Aside from the fact that I'm older than you, remind me why you're not naked in my house again?

Oh thats right, that guy with doughy man-teats.

 

[anabolicmd]

Aside from the fact that I'm older than you, remind me why you're not naked in my house again?

Oh thats right, that guy with doughy man-teats.

Oh, so she did hook up with biteme?

 

[flexygrl]

WHAAAAAA? My husband doesn't have douhy man tits! That's not right!!! Would you really have me naked in your house?

 

[javaguru]

well see here is the difference. most end users know didly squat about computers because they have never been taught the basics or never had a PC to be familiarized with them. however, people in the IT field have neen taught in one way or another. and yet, they always seem to not correct the problem or make a new problem.

lets be honest here. if most end users knew the basics, there wouldnt be a need for so much support right? but my problem here isnt support. i know enough about computers to fix them whenver something breaks down. its LANs that i dont know anything about

1. In my situation the reason I get support calls from moron end users is they choose not to write down critical information. They are given a number with a unique user id and password for the 3rd party that provides their EDI mailbox. There is a hard copy bright red document telling them to copy and store the info. They also have a readme with the software as well as a prompt when they go to the screen where they enter the information. Finally, an account rep calls them after we ship the software to determine "customer satisfaction" and tell them to keep a hard copy of the info as well. Yet, we still have morons who fail to follow simple directions calling me because, "our software doesn't work after we upgraded to a new machine.". I have no fucking idea what their unique info might be and they need to contact their EDI provider if they fuck up and don't write down a hard copy.

2. You often get what you pay for. If you got a network guy from an MCSE mill with no experience for a job that pays $12.00 an hour then you deserve what you get. Also, asking a programmer to solve a wan/lan network issue is like asking a general practicioner to do brain surgery, not a smart idea. The fact IT was so hot in the late 90's attracted a lot of people motivated solely for monetary gain with little "love" for the job. Find yourself a true "computer geek" and you won't have a problem.

BTW, I've worked with an owner of a 50 million dollar business who bought a $300.00 second hand e-machine from the "guy on 2nd shift who knows a lot about computers and is my IT guy" to run his order system. I actually had to teach him how to navigate windows and copy/paste over the phone and guide him through a basic install. Likewise, the "power user" is most often the biggest pain in the ass to work with because "they know a lot about computers" and second guess someone who understands what is actually going on.

 

[DepressiveJuice]

1. In my situation the reason I get support calls from moron end users is they choose not to write down critical information. They are given a number with a unique user id and password for the 3rd party that provides their EDI mailbox. There is a hard copy bright red document telling them to copy and store the info. They also have a readme with the software as well as a prompt when they go to the screen where they enter the information. Finally, an account rep calls them after we ship the software to determine "customer satisfaction" and tell them to keep a hard copy of the info as well. Yet, we still have morons who fail to follow simple directions calling me because, "our software doesn't work after we upgraded to a new machine.". I have no fucking idea what their unique info might be and they need to contact their EDI provider if they fuck up and don't write down a hard copy.

2. You often get what you pay for. If you got a network guy from an MCSE mill with no experience for a job that pays $12.00 an hour then you deserve what you get. Also, asking a programmer to solve a wan/lan network issue is like asking a general practicioner to do brain surgery, not a smart idea. The fact IT was so hot in the late 90's attracted a lot of people motivated solely for monetary gain with little "love" for the job. Find yourself a true "computer geek" and you won't have a problem.

1. as i stated, there are alot of dumb end users but that is because they have no training on PCs. also, it might be new employees who have no idea how that entire procedure works.

2. we didnt hire a software programmer to do our LAN (he charges too much for that). we hired someone who connects LANs for this building. we need both of them to talk to each other so we can make the software work in both offices.

there are more dumb IT people than there are end users...% wise

 

[TheProject]

he stole DOS from steve jobs

Yep, you're now officially a moron.

 

[Code]

1. as i stated, there are alot of dumb end users but that is because they have no training on PCs. also, it might be new employees who have no idea how that entire procedure works.

2. we didnt hire a software programmer to do our LAN (he charges too much for that). we hired someone who connects LANs for this building. we need both of them to talk to each other so we can make the software work in both offices.

there are more dumb IT people than there are end users...% wise

Software programmers to connect LANs?????

 

[TheProject]

Software programmers to connect LANs?????

Duh, man.

What else would they do?

Write code?

 

[Code]

Duh, man.

What else would they do?

Write code?

Usually network architects and admins do this.

 

[TheProject]

Usually network architects and admins do this.

Well, fuck.

What're the telecom people gonna do?