10 signs IT is wrong for you

A lot of this seems to apply to IT support jobs
 
I'm sorry, but after hours I want to be with my family, not giving some $luser after-hours support to help $luser finish a job when $luser was goofing off the whole day.

Should a server go down, then it's a different matter...
 
I'm sorry, but after hours I want to be with my family, not giving some $luser after-hours support to help $luser finish a job when $luser was goofing off the whole day.

Should a server go down, then it's a different matter...

Quite right!!!

The list doesn't apply to me except I can't stand losers who think they know everything and stuff up a machine and I really don't work well with people, which is why I am working on a backend of an online IT shop, I just work with products and only have my bosses to answer to :) plus I'm my own boss as I work from home - my own time, my own hours, and I can easily take a few days off without having to ask the bosses :D
 
Yeah that does sound like mostly IT support. I also think the multi tasking one is not really relevant to developers and architects.
 
Yeah that does sound like mostly IT support. I also think the multi tasking one is not really relevant to developers and architects.

I think multitasking is relevant for developers. I've worked on multiple projects, while providing bug fixes to already completed projects if they are required, while also having to sit in meetings that don't really concern me, or update project managers, team leads and other curious parties on the state of my portion of the project, and liaise with the business analyst/s to get clarification or let them know about errors in their spec. And of course update the documentation for code I've written already.
 
I'm sorry, but after hours I want to be with my family, not giving some $luser after-hours support to help $luser finish a job when $luser was goofing off the whole day.

Should a server go down, then it's a different matter...

Ja, don't you love those $lusers that logs a call 5min before you suppose to go home in the afternoon, then they tell you they had the problem since the morning.....
 
I think multitasking is relevant for developers. I've worked on multiple projects, while providing bug fixes to already completed projects if they are required, while also having to sit in meetings that don't really concern me, or update project managers, team leads and other curious parties on the state of my portion of the project, and liaise with the business analyst/s to get clarification or let them know about errors in their spec. And of course update the documentation for code I've written already.

But often do you switch between tasks? Its fine to work on multiple projects, so long as you have a few uninterrrupted hours per project. Developers tend to concentrate on one task and finish it, whereas your managers and salesmen can jump from task to task quickly.
 
4 and 10 don't apply to me at all.

System Admin and I vary rarely, if ever deal with users, as for phone off, I am part of a team that supply 24 hour support, when I knock off someone else takes over.

Will agree to the whole patience thing but on the giving up to quickly some IT never know when its time to ask for help trying forever to fix things that could have taken 5 seconds if they asked someone in the know.
 
Probably falls under patience but the ability to simplify and explain things to technologically challenged people.

Trying explaining why the RAM has gone bad to a person who thinks RAM & hard-drives are the same things.
 
Ja, don't you love those $lusers that logs a call 5min before you suppose to go home in the afternoon, then they tell you they had the problem since the morning.....

Calls like that get marked as low priority and dealt with next week.
 
Sounds almost like a list written more by a business guy than a IT orientated person.
 
I joined MyBB to learn PC stuff but have no idea if R260 is the name of a small credit card size pc or the price.
 
But often do you switch between tasks? Its fine to work on multiple projects, so long as you have a few uninterrrupted hours per project. Developers tend to concentrate on one task and finish it, whereas your managers and salesmen can jump from task to task quickly.

I've had to switch more often than I'd like. It has led to me further subdividing a task into smaller pieces that I try to fit between interruptions and changing my working hours so that I'm still at the office when all the manager types have gone home, or getting there before they even arrive (It's amazing how much work one can get done after 17:00 or before 8:00)
 
I am front desk consultant and knows that people can be difficult. 99% of the customers told me that i'm very patient when trying to resolve or truobleshooting their pc. So i have atleast one of the requirements for the IT industry
 
Calls like that get marked as low priority and dealt with next week.

Lovely.

Had one such call this afternoon.

I went out to my car, and just as I was about to leave company premises, remembered my jacket.

Parked car, went into office. Got told that $damager was looking for me.

I just went home, it can wait for tomorrow, had enough of $damagers asking me at the last minute to cut a cd or some other stuff which they forgot about. There was NO email from that particular $damager.

Tough, that's life.
 
Top
Sign up to the MyBroadband newsletter
X