Knowing to Google the error code then making the error code stop is knowing how to do your job. That’s my job as well so I wish you all the luck in the world.
It’s hilarious that people think I’m some kind of problem solver for all of their random issues they send over. I’ve even told them when they send me their errors - I literally copy and paste it into google (and now bing b/c google is becoming cluttered with garbage). Some of them just can’t wrap their head around just googling the error code or error string.
Maybe the one thing we can do is filter out the irrelevant answers, and choose the correct/closest solution, that way they don’t have to wade into the mess
I work in IT. So the lie is I know what I am doing, when all I do is google the error code and hope for stack overflow has an answer.
Knowing to Google the error code then making the error code stop is knowing how to do your job. That’s my job as well so I wish you all the luck in the world.
30 years ago you would have checked the manual or read the documentation, not much different just a little faster these days
30 years ago, manuals were worth the read.
I was doing IT 30 years ago.
Back then you’d post a question on USENET and get an answer back from the guy who wrote the program you were asking about.
It’s hilarious that people think I’m some kind of problem solver for all of their random issues they send over. I’ve even told them when they send me their errors - I literally copy and paste it into google (and now bing b/c google is becoming cluttered with garbage). Some of them just can’t wrap their head around just googling the error code or error string.
Maybe the one thing we can do is filter out the irrelevant answers, and choose the correct/closest solution, that way they don’t have to wade into the mess