4 answers
Asked
1881 views
importance of process of elimination in a computer?
Intrested in knowing more about IT #ITsupport
Login to comment
4 answers
Updated
Matt’s Answer
Closing doors, ala the scientific method, is as important as opening them. So it is incredibly important to be able to troubleshoot systems on a computer and eliminate those that are not a part of a specific issue (if I am having an issue with sound, it's likely not the video card) and focus your time and efforts on the system(s) that could be an issue. There will always be basic questions that have to be answered and, sometimes, an issue simply cannot be diagnosed and a computer may have to be re-imaged /replaced altogether.
Try building your own PC if you have not already (https://www.wired.com/story/how-to-build-a-pc/ ). Experience is the best teacher.
Matt recommends the following next steps:
Updated
Dexter’s Answer
Hi Kefuwe,
Having worked in and around IT my whole career, I would say that the process of elimination is key in being a successful IT technician. Most of the time, you're walking into a situation where there's a problem, and the expectation is that you can solve it right then and there. So then you're sitting in front of that computer or server, with the customer watching you, so that they can learn (and to make sure you're not invading their privacy). From there, you use your own experience (and maybe a google search or two), to eliminate what the problem can be. Slowly, but surely, you whittle down and check the components that could be causing the problem, until you fix it. Then you file that away in your brain and fix the next problem.
I would highly recommend that you volunteer with a nonprofit that provides IT support to those less fortunate. This way you can build up your knowledge base, get a good feel for supporting computers, and get used to working with customers. I would recommend using VolunteerMatch to find gigs like this one: https://www.volunteermatch.org/search/opp149589.jsp .
I wish you the best of luck! And let me know if you have any other questions!
--
Dexter
Having worked in and around IT my whole career, I would say that the process of elimination is key in being a successful IT technician. Most of the time, you're walking into a situation where there's a problem, and the expectation is that you can solve it right then and there. So then you're sitting in front of that computer or server, with the customer watching you, so that they can learn (and to make sure you're not invading their privacy). From there, you use your own experience (and maybe a google search or two), to eliminate what the problem can be. Slowly, but surely, you whittle down and check the components that could be causing the problem, until you fix it. Then you file that away in your brain and fix the next problem.
I would highly recommend that you volunteer with a nonprofit that provides IT support to those less fortunate. This way you can build up your knowledge base, get a good feel for supporting computers, and get used to working with customers. I would recommend using VolunteerMatch to find gigs like this one: https://www.volunteermatch.org/search/opp149589.jsp .
I wish you the best of luck! And let me know if you have any other questions!
--
Dexter
I appreciate it.
Kefuwe
Updated
Mabia’s Answer
I think this question is more generic than just IT. You can use that to any problem solving situation:
1 . Think of what are the possible causes of the problem you're trying to solve.
2. Given the short list from step 1, test the options one by one (process of elimination).
3 . At each step, try to understand what is happening and rethink your options.
4. Repeat, until you have your solution.
1 . Think of what are the possible causes of the problem you're trying to solve.
2. Given the short list from step 1, test the options one by one (process of elimination).
3 . At each step, try to understand what is happening and rethink your options.
4. Repeat, until you have your solution.
Updated
Andy’s Answer
A really simple way to look at this is to just 'split the problem in half'.
For example, let's say there is an issue where a laptop can't print.
Cut the problem in half - can other laptops print to that printer? They can? Great, you now know there is no problem with the printer.
Split the problem in half again. Keep doing this and you'll quickly find the root cause.
It's a simple principle, but even for the most complex issues it can be useful!
For example, let's say there is an issue where a laptop can't print.
Cut the problem in half - can other laptops print to that printer? They can? Great, you now know there is no problem with the printer.
Split the problem in half again. Keep doing this and you'll quickly find the root cause.
It's a simple principle, but even for the most complex issues it can be useful!