Some advice for a n00b

[X-13]

If in doubt, Hanlon's Razor is your guide: Never attribute to malice that which is adequately explained by stupidity.

 

One addition to the sound advice above to simply tell people when you don't know an answer but that you will find out: best not to BS them with some mumbled jargon...

 

Also, get used to explaining things in a very simple way.

 

"I need to do some stuff on the server" will usually do for explaining backend config changes or GPO wrangling.

[pickman]

Agree with all the above. As its been said approachablity and communication are the key I've found.

 

Sometimes instead of replying to an email go and see the user. They tend to like the personal touch especially if it a tricky situation. No misunderstood emails.

 

Started as an apprentice back in 95 and became a network manager in 2000 haven't looked back. But i'm the first to admit i'm not great technically but I can find out the solution.

[Gibson335]

Sometimes instead of replying to an email go and see the user.

 

It's easy to fall into this trap - rule of thumb is, if it's quicker for the user to resolve via mail, then do so...if it's uncertain, pay a visit if at all possible (they may be teaching, remember...).

[Dos_Box]

Indeed, backups, replication, tapes, cloud, anything you can think of is usually a good idea when it comes to backups!

 

And check your backups that they work correctly!!

[danbuntu]

Obey Wheatons Law

[markwilfan]

Remember that every day is a school day and that security and convenience are directly opposed

[X-13]

Obey Wheatons Law

 

"In all circumstances Wesley needs to shut up"?

 

[DJ-1701]

"In all circumstances Wesley needs to shut up"?

 

 

Is Wesley a popular name these days?

[Grey-gear]

Be patient with the users, they are all have different levels of IT knowledge (this can be hard with some users than other). Best advise is just talk to them without using big technical words where possible and be polite.

[witch]

My most precious resource is my "How to..." file. I keep instructions on how to do anything I come across. It is easy to do something if you do it all the time but encountering something you haven't seen for a year is when you find your memory lets you down, and that's where the "How to.." info comes in handy

[Novalee]

I was in a similar position to you about 3 years ago. I don't have any qualifications in this field but began working in it all the same.

 

I've learnt so much along the way through just being polite, friendly and having a laugh with my co-workers. They have taught me a lot. Be independent, but also remember that there is a wealth of information right in your office from the rest of the team so if you can't figure out how to do something, don't be afraid of asking them for help.

 

I agree with @witch. There are lots of jobs in school which you'll only do once in a blue moon. Create a word document or similar and write how to do them. You'll forget if you don't do it all the time. I spent the first year of this job trying to find spare bits of notes in my notepad on how to do something, and the 'How To' document is incredibly useful. Include screenshots in it etc. so you can always remember how to do different things. You will learn a LOT in the first 6 months and you'll soon be looking back wondering how on earth you learnt it all!

 

Best of luck!

[hardtailstar]

Remember everything will be your fault even if its the users or outside suppliers/contractors.

 

Be calm, patient and understanding.

[Ephelyon]

security and convenience are directly opposed

 

That doesn't mean you can't always have both...

[pantscat]

The things that'll get you far in the workplace in my experience are:

 

1. Always be polite, calm and patient with people. Even if they're incredibly annoying.

 

2. Be honest.

 

3. Document everything. You won't remember that obscure registry fix in two weeks time.

 

4. Try to specialise in something you enjoy. There's nothing better than being paid to do something you find interesting. (Although a lot of us are still working on this!)

 

5. Don't be afraid to do something, and also don't be afraid to say that you don't know how to do something. If you don't know - say so, but say that you'll look into it. And ask for help when you need it.

 

6. Remember names.

 

7. Trying to get a problem fixed with a 3rd party? Don't be aggressive. Explain the issues clearly and ask for their help. You're more likely to get a swift resolution by being reasonable.

 

8. Never belittle someone's IT problem - it might seem minor to you, but it could be enough to send them to a meltdown and ruin their whole day/week/month.

 

9. Always try to think of the bigger picture. A quick fix is great, but no good if it's going to create a lot of work further down the road. Do it properly the first time.

 

10. Never underestimate the benefit from having a break. It'll clear your head and make you more effective.

 

11. Being approachable is important. Try not to be an IT-hobbit living in a dungeon that no one dares visit. Walk around - say hi to people.

[elsiegee40]

If in doubt, get your phone out and photograph it.

 

Handy for noting error messages, remembering which cable was plugged into what hole, condition of a piece of equipment...

[Boredguy]

If in doubt, get your phone out and photograph it.

Just be careful what your photographing as you don't want to get into trouble.

[DJ-1701]

Whenever purchasing look at future proofing (especially servers), sage advice at the best of times, but certainly when you don't know what your next budget will be.

[sidewinder]

Never underestimate the stupidity or lack of common sense when dealing with end users. They really haven't a clue!!

 

Or perhaps see them as normal people who happen to do a different job than you. Treating people with contempt just means they'll end up hating you too.

[Norphy]

Don't hide away in the IT office no matter how daunting it seems. Do make sure you're seen and talk to people.

 

In schools, I suggest taking your coffee in the staff room during one school break time every day at first so that people can get to know you

 

Just don't let them sucker you into taking time out of your lunch or breaks. You need your breaks just as much as they do.

[DJ-1701]

Just don't let them sucker you into taking time out of your lunch or breaks. You need your breaks just as much as they do.

 

Some of us are still attempting to learn this one!

[X-13]

Just don't let them sucker you into taking time out of your lunch or breaks. You need your breaks just as much as they do.

 

In addition: You can take your break/lunch whenever. Teachers have set times for it.

 

It doesn't hurt to push your break/lunch back a bit to get stuff done when people are out of class.

[Norphy]

In addition: You can take your break/lunch whenever. Teachers have set times for it.

 

It doesn't hurt to push your break/lunch back a bit to get stuff done when people are out of class.

 

While in principal I agree completely, that can be a double edged sword, especially if you're the only tech on site. There's always going to be one moany individual who will have a go at you for taking a break during lesson time because they forgot what colour the Any key was again.

[X-13]

While in principal I agree completely, that can be a double edged sword, especially if you're the only tech on site. There's always going to be one moany individual who will have a go at you for taking a break during lesson time because they forgot what colour the Any key was again.

 

I tend to play it by ear, TBH.

 

Take breaks at the same time as staff, unless I KNOW there's something I need to do during break/lunch.

[Garacesh]

I take my lunch at 12:00 usually, and there's plenty of "I know you're on your lunch.." 'cause I take it at my desk (I don't really want to sit in the staff room with all the different cliques of staff members that I'm not part of and listen to all the gossip.. Did that for about two days when I started and haven't done since) and depending on what the question is, I'll either do it, or I won't. If someone comes down needing to check the cameras, I don't mind doing that whilst I eat. If it's print toner that needs replacing, it can wait (or I send the other tech to do it). If it's urgent I'll pause my lunch and get back to it when I can.

 

Mostly, though, I just take my lunch at 12:00 because I work 8-4, so it's a nice midpoint

[cherd84]

If in doubt, get your phone out and photograph it.

 

This is always useful when taking apart equipment, even if you've become familiar with it.

 

Also, when taking equipment to pieces, make sure your work space is clear. It's very easy to put something back together and be a few screws short if it's a mess!