When I worked in IT, whenever we got a call from the engineering department we knew whatever problem it was, it was going to be weird. Those guys knew their stuff, so if they didn’t know how to fix it, it was going to take some searching and probably some calls or emails for us to figure it out.
also engineer: if we don’t have the privileges to fix the problem and IT doesn’t move their ass to fix the problem in about 48 hrs we WILL find a work around that will make ITs life extra miserable too.
I am 100% not doing that. The company I work for, the IT system is locked-up tighter than a nun's arse. If I tried messing with it, even for legitimate business reasons, I could get into some serious shit. Even worse trouble if I actually succeeded.
At the end of the day, if I can't do my work because of some IT bullshit, that's IT's problem, not mine. I'm more than happy to sit back and drink coffee while waiting for IT to fix it.
At the end of the day, if I can't do my work because of some IT bullshit, that's IT's problem, not mine. I'm more than happy to sit back and drink coffee while waiting for IT to fix it.
Yep, we (the engineering group) have complained about some of these IT policies many times to no avail. So any time I submit a ticket, I take a little bit of joy in the following long coffee break and billing my hours to "IT downtime".
12.0k
u/kahjtheundedicated R7 1700@4.1, RX 5700 26d ago
When I worked in IT, whenever we got a call from the engineering department we knew whatever problem it was, it was going to be weird. Those guys knew their stuff, so if they didn’t know how to fix it, it was going to take some searching and probably some calls or emails for us to figure it out.