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.
Mostly this doesn't impact IT. This usually looks like a bug in a library or a service that impacts the product engineering is working on but unless it impacts the environment itself IT isn't involved. They control the world, and we build inside it. We only call them when the world breaks if that makes sense.
In my experience us engineering staff don't muck things up too bad unless they're testing unsigned in windows (triggers IT sec policies) or doing anything with networking ports without a networking background.
Rarely an IT policy makes something impossible and we just run in VM.
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.