I’ve fired off plenty of screenshots hoping someone else would save me five minutes of reading, and it never helped. You hit an error, take one look at the message, and drop it in Teams with a quick “anyone seen this before?” hoping someone will come back with an answer.
That’s what I call outsourcing your problem.
Asking for help is fine. It’s part of working in tech, but how you ask matters. When you just forward the problem, you’re asking someone else to start cold. They don’t know what you’re doing, what changed, or what you’ve already checked, so they have to do all the discovery you skipped.
If you want real help, bring context. Read the message and try to understand what it’s saying. Even if you don’t get far, it shows the other person where to start. Compare these two:
“Anyone know how to fix this?” vs. “I ran X and got this error. It looks like Y is failing, but I’m not sure why. Can you help me read it?”
The second one tells people you’ve tried to think it through. They’ll respond faster, and you’ll learn something instead of just copying a fix.
Most people don’t expect you to know everything, but they do expect you to care enough to figure out what’s happening before asking for a rescue. So before you hit send on that screenshot, read the error, think about what changed, and try to narrow it down. Then, if you’re still stuck, ask for help with context.
This doesn’t mean working everything out alone. If it’s a common error with a common fix, and I can find the answer in the archives by myself, I’ll take it. The case where I try to stay with it is when I barely understand what I’m trying to build in the first place.
That happened when I installed Proxmox for the first time. The storage pool I set up was only recognizing some of the space on my drives, and I didn’t notice until I was moving my media library onto a VM and started getting errors saying I was out of drive space. I spent the first few hours learning how to troubleshoot drives on Linux, mostly reading Stack Overflow and Reddit posts, trying to figure out how to even figure out what was happening. It came down to how ZFS handles drives of different sizes, which was a gap in my understanding and not something wrong with Proxmox.
I could have reached out to someone I knew who probably would have steered me in the right direction sooner. I didn’t, because I barely understood what I was trying to accomplish, and I wanted to use it to fill in that gap. I also didn’t want them to feel like they needed to take responsibility for my problem. That second reason is the part of this I care about most. Handing someone a screenshot and nothing else hands them the problem too.
The best fixes I’ve learned came from slowing down long enough to understand what the system was actually saying.