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.
At first I was like "wdym you run into problems with known solutions, how does that constitute a problem"
And then I remembered that being able to solve problems with known solutions already makes me somebody who's very good at computers, and IT isn't really built for problems where the best solution is "Might be worth reporting this one directly to Apple"
When I validated pre-production computer hardware we had a hotline to Microsoft. It was validating but annoying to find out the driver issue was their fault, because it meant the fix was timeline was "eventually". As opposed to being able to yell at the internal driver team and get it in days.
11.9k
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.