It’s kind of obvious but when troubleshooting really try to think about things logically “What works? What doesn’t work?” goes a long way.
It’s pretty easy to get worked up and take leaps like “This printer must be broken” for example but if you think about the processes along the way it can help. Are there any signs of life? Has this ever worked? Did it work on a different computer? Is the cable fine? And so on.
Basically taking a step back and being more methodical.
It’s kind of obvious but when troubleshooting really try to think about things logically “What works? What doesn’t work?” goes a long way.
It’s pretty easy to get worked up and take leaps like “This printer must be broken” for example but if you think about the processes along the way it can help. Are there any signs of life? Has this ever worked? Did it work on a different computer? Is the cable fine? And so on.
Basically taking a step back and being more methodical.
There is a alternative for this. It’s called Rubber Ducking.
Basically if you can break it down so you can explain it to a rubber duck (preferably on your desk) then you probably can find the issue. :)