My grandma had a prestigious tablet which was bootlooping randomly. The service store claimed it was fine and didn’t honor warranty multiple times. Well, this was a shitty alibaba rebrand anyway.
I’m pretty sure that happens because the user is more careful about what they do, avoiding doing whatever caused the problem while an IT person is watching
In my experience, random failure with random auto-fix is exclusively a windows feature. Turning it off and on fixes the majority of windows glitches.
I just tell people the computer is afraid of me. Because it is.
It’s a bit of a curse, so often I come in and things magically start working… But that’s hardly satisfying, and the person that needs help just knows it’s going to bite them again… So I get to guess why it broke before it behaved for me and hopefully figure it out and fix it despite it currently working right now.
You embarrassed the computer back into working. Pat yourself on the shoulder.
I had a coworker who had constant issues with her laptop. Whenever she tried showing it to me, the issue magically fixed itself.
After this happened multiple times, she would just ask me to quickly touch the laptop to fix it. Worked every time!
“Come, touch my computer parts”
Sounds like she might have been hitting on you.
It’s part of the class package. We auto-resolve issues under a certain level of difficulty just by being nearby. Pretty nifty.
We should sprinkle IT people around the offices like wifi routers. To project their aura of auto-resolving constantly throughout the workplace. As a programmer I have more of an aura of auto-breaking any system that I’m near so hopefully they cancel out
This only works on others computers.
If the wizard themselves experience a minor irritating tech issue, then it stays permanently and forces the wizard to use a convoluted work around instead of asking another wizard for help (this would fix it)
Haha! Yeah, that’s pretty much it :,D
I call it the blue thumb.
Magic Fingers.
One of my previous tech jobs used this strategically. We would just send like a vague “hey could I get your help for a sec” which was code for “some trivial thing that has never failed before is failing now but if it thinks I’m wasting your time it’ll start working”. Half the time when the other person showed up we’d just talk about random stuff while the person tries the thing again and it would start working no need to ever know what the bug was in the first place
I’m in IT, but not that kind of IT.
Last week I afflicted myself with the Location Services are turned off bug by installing the 23H2 update to duplicate an issue a user in my work area was having.
When I called desktop support, we could not replicate the issue after he remoted in.
He closed the Remote Desktop connection, and the issue reoccurred.
He remoted in. The popup vanished as soon as he connected. We couldn’t replicate the issue. He seemed dubious now. He disconnected. It occurred. I got a screenshot. He reconnected. We looked at the remote connection settings. Remote connections were set to override location. Disabled that. Issue presented. We both had a good laugh.I worked in IT for 25 years and this was true for a large majority of calls I got over the years. I called it the IT intimidation rule. LOL
One time, I was staring at a piece of code for a solid 10 minutes or so, and could not understand why it gave me a compile error.
So, I ask the senior for help, start explaining what I’ve been trying to do, scroll down to show some other code snippet, scroll back up and the compile error was gone. My IDE simply had not re-rendered properly. I have rarely sweared as much as in that moment.Sometimes you just have to book a doctor’s appointment to break your kid’s fever and make the slapped cheeks appear.
