Cause literally everything is in the wiki, written out very simply. Rewriting that in a chat and email would be counter productive.
I get your sentiment on people skipping the reasearch part and jumping to asking help but I wouldn’t say everything is documented tho. Although for the few problems that I did have arch documentation was pretty nice. I myself have an bluetooth bug that I eventually gave up as I couldn’t find a fix to it, that’s the only post I made with this account if u want to look it up. With things constantly changing and the infinite possibilities of config, there will always be some unknown bugs or issues that no documentation can cover.
As a noob to Linux: THERE’S A WIKI? Awesome!
As a mechanic: Everything I deal with comes with an instruction manual that has the steps written out simply… for a mechanic.
If I didn’t ask the simple questions when I first started, despite having the manual available, never would have learned the basics from someone who knows.
I’m not trying to sound combative or anything, just that sometimes a person needs a small stepping stone of an answer to progress.
It’s the same shit as working tech support, no one EVER reads manuals or does standard troubleshooting, they instantly jump to asking people for help which forces them to just read out the manual and troubleshooting steps first instead of actually helping those who need help…
If people could learn to take care of the fundamentals themselves and only ask for help when actually needed, everyone would be better off.
don’t even need that, i’ve interacted with several companies that use a simple chatbot with pre-programmed responses and honestly? It’s pretty nice and doesn’t feel like bullshit.
Biggest issue is probably that people tend to forget it’s not a human, and ask it 10 run-on questions which makes the software cry.
They have to specifically tell you to ask one question at a time and use as few words as possible…
As a fellow ex-help desk guy :tm:. I just want to say that A) I feel you but also B) the very fact that you know no one reads manuals should be an indication that expecting them to is a flaw. Instead most people generally do better with hands on coaching. Idk about your job, but back when I was working help desk I got way better results when I let people just be people and patiently guided them through the steps. Most of them catch on eventually
I hate that, because when i call tech support i have to listen to them walk me through the basic steps before i get to the parts i need. I try telling them I’ve already worked through basic troubleshooting, but most of them are reading a script for every idiot that calls.
