What does a tech really need to know?

[citizensmith]

What does a tech realy need to know?

I figured a list of things that are considered esentials to know. Like on a job skills requirement sheet. Maybe it would reduce mine and others posting narky coments when those "Duh did'nt you know that" type questions are asked.

how to
reset, bypass, recover OS passwords
ID those unknown devices
use Live PE disks
recover data from non booting pc
setup server dhcp, dns, printers
check event logs for errors
search for error messages online
use tools from (nirsoft) etc

know when you can't actualy do something. dont wing it.

If this is a dull idea do say so . If it works may be worth a sticky??

 

[NYJimbo]

How to think like a computer.

 

[NETWizz]

It is not a dull idea, but perhaps not ready to make it a sticky. It is really hard to quantify exactly what a tech needs to know.

This totally depends on what a tech's duties are as assigned. For example, I don't work on computers or anything residential, so my skillet may be significantly different than an end-user or desktop-support tech. That said, I HAVE worked on these things in the past.

Generally speaking, I prefer working with network switches, routers, circuits, protocols, VOIP, etc., but I also work with servers, Active Directory, vitalization, High Availability, Storage/SAN, and security. I abhore working on any residential computer... The problems pretty much all fit into A) I got spyware/ad-ware -help B) It won't start-up C) I can't Print or get Online D) I can't login E) my data got lost and F) it's slow..

It is the same old story, "I need you to recover all my pictures, and documents, fix this thing so it starts up, make it secure so I can do everything but install Spyware, put all my programs back on, teach me to use my programs, make me able to print and get on the Internet... and be sure to make it FAST and keep ALL costs under $110."

^^^^ This is why I don't do residential. Too much aggravation and frustration, to fix something that is either TOO broken to be reasonably /cheaply fixed or user-error.

The reality is that what I have to know is totally different. I don't really need to know how to recover OS passwords or use Live CDs for example... and it is pretty unlikely I am going to be hunting down the Device/Hardware IDs like PCI\VEN_8086&DEV_2E17&SUBSYS_027F1028&REV_03... Instead, I generally assign that type of work to someone else.

Often times, I am NOT called in to fix anything at all. Sometimes I am more of a diagnostician than a technician...



One thing for sure though, and this is where I need improvement:

All techs need to KNOW how to sell!!!

 

[SpaceSquad]

how to think like a computer.

10001010001 001001010100 10101 0101010!!!

0101010001010 0001010101010 1101010101000!

 

[scott00049]

I think that the list of what a tech needs to know would vary based on the majority of the work the tech will be doing.

Break/fix - lots of the items on your list, but not much network stuff (routers, switches, etc.)

Network, SMB provider - More on the network side of the scope of things.

Perhaps to make it a sticky, it could be divided into categories of specialty.

1. Break/fix
2. Networking
3. MSP & SMB services
4. other

-Scott

 

[ohio_grad_06]

Main thing might be to be proficient with Google.

Know your limits, be able to search out what you don't know and be willing to learn.

 

[Markverhyden]

What does a tech realy need to know?

Their limits.

 

[coffee]

What does a tech realy need to know?

I figured a list of things that are considered esentials to know. Like on a job skills requirement sheet. Maybe it would reduce mine and others posting narky coments when those "Duh did'nt you know that" type questions are asked.

how to
reset, bypass, recover OS passwords
ID those unknown devices
use Live PE disks
recover data from non booting pc
setup server dhcp, dns, printers
check event logs for errors
search for error messages online
use tools from (nirsoft) etc

know when you can't actualy do something. dont wing it.

If this is a dull idea do say so . If it works may be worth a sticky??

Depends on how good you want to be. But what it boils down too is that you need to know enough to perform your job adequately. If your specializing in networks then you should know alot about networks. If your concentrating on a particular type of customer like residential you should be familiar with the problems they run into and how to overcome them.

To be honest, Alot of things I dont bother to memorize them because that information is freely available doing a websearch. But you have to know what to look for and how to apply it. NETwizz made a great point in that you have to know how to sell is a biggy. I can go a little further and add that you have to know how to handle people and how to interact with them successfully.

Many techs loose alot of sales because they do not have alot of experience dealing with people in that fashion. You can know all about computers/networks/ect.. and still not be successful in the business. You also have to sell yourself to the customer.

On the subject though of techs posting "stupid" questions I can only say that alot of these questions can be websearched. But alot of techs apparently can not do that or do not wish to do that. In either case this is going to look bad for that tech. Seems alot of posters want a quick answer with minimal effort involved. However, Its by that effort that you learn. Otherwise you end up asking the same questions or related ones over and over again.

The best advice you can ever get is from someone criticizing you. Whether its in a forum or over the phone or in person. They're criticism is what you should learn from and be glad you got it. The "Inferior tech" will just lash out at them in defense mode and not pay any attention to the criticism given.

In the case of "You should already know that" in a post, They are most of the time right. You should know that and you should thank them for their answer. Its better to ask instead "Can you recommend a link to where I can read up on this particular problem?".

While we are at it - Another thing is treat your fellow techs with respect. Not everyone knows everything.

Have a great day,

coffee

 

[citizensmith]

thanks everyone for your thoughts and insites. Makes great reading, full of good advice. Especialy regards the business \ selling points,

 

[mr m]

Don't forget about customer relations. If we can't deal with people all of our technical skillsets are useless.

 

[AndyM]

Like this guy here, I need to be able to explain things to my customers in a nice, friendly way...

If that doesn't work, well, I dunno.....

Andy

 

[mraikes]

What does a tech realy need to know?

I figured a list of things that are considered esentials to know. Like on a job skills requirement sheet. Maybe it would reduce mine and others posting narky coments when those "Duh did'nt you know that" type questions are asked.

...snipped....

How would such a list reduce the snarky comments?

Failing to measure up to a skills assessment isn't the poster's fault. There's no standard for who joins TN as a member. No expression or acknowledgement of even the most minimum of tech or business management skills is needed to become a member. Accumulating a list of skills or traits won't have any impact on that.

All that is required is a vaguely expressed desire to perhaps, someday, maybe, start, or work for, or visit, a repair business and the "Welcome to Technibbles!" will roll on in. Not even that really - just hint that you are (or want to be, or might be someday become) a computer related "tech" of any kind and step onto the welcome mat.

Don't get me wrong, I love TN and have spent little-to-no time on any other forums for years now. But TN is open to anyone except those foolish enough to outright admit they're an end user. The price we pay for that openness is the necessity of overlooking posts/threads by overly inexperienced "techs" if such things bother us.

 

[smashedbotatos]

There is fixed the Nirsoft part for you.

That is a pretty slim list honestly. Then again it all depends on what you plan to do and what services you will offer.

Remote support requires a similar, but different skill set than on site residential repairs. Residential repairs require a very different skill set than working with a SMB.

I know people that could fix a PC no problem, but couldn't configure a simple home network with DHCP switches. Even after all that you still need social skills, and the mindset of an honest salesman. I really don't think there could be a comprehensive list.

I for sure know, a grad straight out of college with no business experience, but a BS in Computer Science or Networking. Would most likely have their business fail after the first year on their own.

 

[bertie40]

What a tech really needs to know ?

Easy.
Learn how to SEARCH

One of my catchphrases

"it's not a case of knowing all the answers, it's a case of asking the right questions".

(...... And not to piss off Xander ).
Sorry.

 

[frederick]

Many amazing answers have been made. For me, I think it really comes down to what the tech does.

Things boil down to either Network or System. Both equally their own separate mammals.

As a technician, you should know the basics of both. i.e. Passed the A+ and Net+. As a senior tech (levels 2 and 3), you should be on the MCP track or the Cisco (or other proprietary networking equivalent) track.

As an Administrator, you are either a Network or a System. Network Admins know the ins-outs of the interwebs. They need to know the fundamentals of systems as well.

As a SysAdmin, they should live and breathe the OS, the different servers, etc. But they need to know the fundamentals as well. Even SysAdmin can be broken down into Database, as well as others.

Looking at my upbringing, I know Networking and I know Network Security (more on an enterprise level than a SMB/Personal). Hence why I was in Network Security. Honestly, this field is too broad for a single person to do it all/know it all. Therefore I think it really boils down to what they want to do.

 

[ohio_grad_06]

I'm probably the odd man out. I don't have my A+ etc. I went to school for four years but found I learned most off what I know on the job. Plus I've just been playing with computers for years. My first computer was a Commodore 64 when I was 5. Always just enjoyed technology.

 

[HCHTech]

What a tech really needs to know ?

Easy.
Learn how to SEARCH

One of my catchphrases

"it's not a case of knowing all the answers, it's a case of asking the right questions".

(...... And not to piss off Xander ).
Sorry.

^^THIS. Honestly, I think a lot of it boils down to being a good detective. Know how to find the right clues, then you can research properly if you don't know the answer. That, and having a good demeanor and way more patience than normal if you're doing residential. The Xander part is a bonus. (Ducks)

 

[CTech]

Common Sense, Positive Mental Attitude and know how to use Google.

 

[16k_zx81]

I used to live with a guy who was studying to be a physiotherapist.

Most of the stuff they were learning in the course was boiled down to: "diagnostic reasoning"

- the ability to take a bunch of symptoms, then *quickly* and *accurately* work out cause, then implement a lasting, effective, *solution*.

Anything Techs "know" is gravy. But without good Diagnostic Reasoning, they can "know" all they like and still not be much use at all... First year uni/college grads are often a good example - all theory and no experience

--

But if we're talking about "self-employed" techs, the list might be a wee bit longer

 

[techithur]

Main thing might be to be proficient with Google.

Know your limits, be able to search out what you don't know and be willing to learn.

Thanks a lot for this thought. It cleared up my mind.. You're so great man..