this post was submitted on 20 Aug 2023
40 points (83.3% liked)
Asklemmy
43513 readers
1301 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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. :)
In the absence of a rubber duck a co-worker will do!