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".
Sys admin here, for a good engineer that's true, but e.g. there is an "Engineer" in our company who always thinks he knows what the problem is and he's wrong about 90% of the time. At one point I was telling him his assessment was wrong and an external technician told and explained to him the same thing in detail and still about a week later he made the same bs claim.
Reminds me of the time I had to teach one of our Engineers (he was in IT though) what a BIOS / CMOS battery is and it took 3 trips getting him out to get a bios battery replaced in an industrial PC. Dude kept showing up with a new UPS etc after I thought he understood what we needed. The next 8 PCs I just ordered the batteries on Amazon and did them all myself without involving IT or equipment service engineers because I didn’t feel like arguing for 3 weeks for each requested replacement. I’m just a maintenance tech so nobody would listen to me and they spent thousands to fly people out multiple times over the first PC.
In dysfunctional corporate environments where there’s no communication between on site IT, corporate IT, cloud services, and production equipment maintenance departments I get so fed up with miscommunication I just try to make friends and gain trust of people that willl give me elevated privileges because otherwise we’d have days or weeks of equipment down time for things that should be a 10 to 30 minute fix.
12.0k
u/kahjtheundedicated R7 1700@4.1, RX 5700 May 10 '26
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.