When does an end user become a technician?

[Crgky127]

I don't know if I can completely define the difference between an end user and a tech, or accurately interpret the mission statement of Technibble, but I do know the types of people I like to see here. That's plural "types", because limiting this site to one type of person means I'd have to keep up with even more sites, and I do need to sleep sometimes. For example:

Computer repair (and related) business owners, that may or may not get involved with the tech stuff as much nowadays.
Technicians (computer repair and related) employed by themselves or by a service firm or by an IT dept.
Beginner technicians that are studying (on their own or in a class), and may think of something I haven't thought of, or point out a tool I haven't tried. (The ones that don't get in over their head with customer computers before they are ready).

There may have been a fourth, but as previously mentioned, I need to sleep. Basically anyone that can post answers and not just questions, that somebody can learn from.

 

[norm1320]

At a bare minimum, a tech should be able to effectively describe a computer problem and what they have already tried.

"computer doesn't boot, need help" doesn't cut it.

 

[Martyn]

At a bare minimum, a tech should be able to effectively describe a computer problem and what they have already tried.

"computer doesn't boot, need help" doesn't cut it.

Pretty much sums it up. In their dialogue of what they have done you will see that they 'know' what are doing and know fault finding. They just need another pair of eyes that sometimes we all need. You are posting on the forums to people who know their stuff so they want the nitty gritty first post. Just recently(not having a dig) we had a network problem connecting to shares and permissions. It took 13 posts before the operating systems came to light! Another person posted a brilliant first post of what he had done and left nothing to guess. It really is that simple.

 

[ATTech]

That's a good analogy.

The crux is you cannot learn how to repair a modern computer from being an end user, you have to learn how the hardare and software work beneath the gloss of the operating system user shell if you are to become confident and competent. Too many think a few years experience is enough - most of our customers have a few years experience using a computer, but they expect a higher level of understanding when employing a technician.

It's funny that this industry is really the only repair industry where knowing what to do, rather than why you do it is tolerated. I haven't meet an auto mechanic who doesn't know the inner working of an internal combustion engine. My plumber has never told me "I've seen this before, If I replace this silver t-shaped thingy, it should start working." I've never seen a HVAC company Google my problem, etc. You need to know how something works in order to know why it's not. Now I'm not bagging on people that Google their issues, only the people who Google the problem and start applying posted "fixes" without knowing what the fixes actually do. Google should be used to narrow down the possible causes, not determine the possible causes

 

[JRDtechnet]

I didn't read this whole thread, but when your not charging a fee (or only enough to cover a slice of pizza) for your services or your coming here asking how to fix a simple issue with your own computer then to me your an end-user and should call a real professional to fix your issues.

 

[Jacob Anthony]

Thanks for all your input guys, I really appreciate it and I promise to learn a lot from it.

I want to become a great technician but in order to do so I felt it made sense to ask what the definition of a technician is so that I can plan a course of action that will put me on the right path.

A lot of you have detailed some of the necessary skills for being a technician, but where can I learn these skills (such as manual virus/malware removal) and what would be your curriculum if you had to learn it all over again.

Thanks again for your support.

I hope that by asking these questions, I help other newbies in the future and make things easier for you guys by at least giving you somewhere to redirect newbies so You don't have to answer the same questions!

Cheers

Jacob

 

[ATSCF]

Google will teach you everything. you have to read alot and test things though. Don't just learn how to do something, learn why you do it and why it works.

Best place to learn is on real systems with real problems. Offer free service to your friends and family to get these systems to learn on. They can't complain if its free, right...?

 

[anonymous Mac Tech]

Google will teach you everything.

I guess you've never worked on Macs or been on the front lines of anything then, have you? I can't tell you how many times I've seen issues that have never been documented (through any kind of search). The best source of knowledge available for any previously seen Apple computer issue is Apple discussions, yet for many issues you'll see temporary fixes or guesses at best. I don't even bother with google most of the time.

 

[ATSCF]

I guess you've never worked on Macs or been on the front lines of anything then, have you? I can't tell you how many times I've seen issues that have never been documented (through any kind of search). The best source of knowledge available for any previously seen Apple computer issue is Apple discussions, yet for many issues you'll see temporary fixes or guesses at best. I don't even bother with google most of the time.

umm... I have been on the front lines for 10 years with servers and workstations. No macs though. I thought macs don't have problems.. j/k

I also run into problems that have never been document but you can pick up bits and pieces from google and sometimes figure it out. I usually drill google every which way with the problem and related problems and file names and or programs. It usually gives me something to start on or an area to focus on.

So when you run into one of othese problems where do you turn?

When that happens to me (usually on servers) I have to call microsoft. They have this hidden manual that only they have access to. Its like the holy grail.

 

[Martyn]

Google is a resource, why re-invent the wheel?

 

[iptech]

Google will teach you everything. you have to read alot and test things though. Don't just learn how to do something, learn why you do it and why it works.

Best place to learn is on real systems with real problems. Offer free service to your friends and family to get these systems to learn on. They can't complain if its free, right...?

Be careful, there's a lot of misguided 'advice' on Google and beyond. Learning 'how to think' is a vital prerequisite before you seek any help on any subject from any medium. With unrestricted global communication there is a growing trend that requires no intellectual/emotional pain or judgement
towards believing in 'what to think', because it's easy, convenient and appears at first look to be authoritative and most importantly it fits your emotional needs.

Check out "my ebook", "my blog", "my testimonials", "my logo", "my Google rank", "my success story", "my credentials", "my self-serving bs..."

...if you believe there really is an easy way to learn.

Knowledge is free, but it's not available freely.