1420
No common rube
(i.ibb.co)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Jul 2024
1420 points (98.6% liked)
Programmer Humor
19572 readers
1623 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
If I am calling IT to fix anything, it's because I've exhausted all the usual things to fix it (restart, clear cache, make sure everything is seated, googled the issue, etc). 9 times outta 10, they're just as stumped as I am and the device simply gets replaced. That 10th time tho it's something I've never encountered but they have.
That's how one becomes IT
I would call IT and give them error codes and attempted remedies. They would do house calls and leave with a few rip its. Everyone in my office usually had my call IT because they (my coworkers and the IT guys) knew I'd at least tried something. If someone else from the office called IT, they knew that I was out of the office or the user was lying about something.
I support doing the troubleshooting yourself. Just be aware, if you call with one of those 9 out of 10 cases, we're still going to have to do ALL of those steps again, so I can document that we tried them before sending any hardware. I've been burned one too many times by someone telling me they've already tried something.
I started in IT before switching to development. I have CCNA, A+, and Apple Pro certifications. I run Arch at home, btw. But when I have to contact IT, usually for something that needs elevated permissions or bad hardware, I'm just another user. It's mildly infuriating to go through all the steps again, even after explaining what I did. I get it, I really do, but it's not fun at all.