The implied problem you aren’t understanding is scope. Restoring your machines functionality and determining that if you do blank the universe breaks IS AN ACTUAL SOLUTION TO YOUR PROBLEM that is in scope and highly efficient. The company probably doesn’t pay you to piddle fuck around nor does it pay the IT guy to make you piddle fucking around work out.
Digging in to the problem and figuring out an exact reproduction of the bug so that a bug can be filed with the appropriate owner of the whatever code and a fix instituted at some point would be far more interesting and fun, even more so if its in code you actually control and you can actually fix it but its likely not actually productive unless you can make a strong case for it.
The cost of fixing your stuff in 15 minutes and having you back in action is about $12.50. The cost of spending 3 days on it is $1200. Surely you understand why it works the way it works.
c0mbatbag3l@lemmy.world 11 months ago
Damn, answered your own question. Have you tried not doing the thing that breaks the computer?
Skates@feddit.nl 11 months ago
Yeah, let me not do my job anymore, so you don’t have to do yours.
Goddamn IT, man. Every single time.
shiftymccool@lemm.ee 11 months ago
Your job is to break computers? If not, my guess is that you can do your job in such a way as to not break the computer. If not, the company really needs to reassess how you’re job is done
c0mbatbag3l@lemmy.world 11 months ago
If it’s ACTUALLY part of your job I’ll care, if it’s some bullshit thing a wannabe IT user did to fuck their shit up that has nothing to do with their job (99% of the time it’s this) then fuck you.
It’s a business machine, not your personal test lab. Goddamn users, man. Every single time.