Oh, on that I totally agree. And not just with Microsoft with everything I run into Microsoft is especially bad because their attitude seems to we need to do something. You don’t need to know what it is and we’re not gonna tell you how long it takes so just fuck right off Which is monumentally annoying of course Apple does give a bunch of code and stuff for errors when something goes wrong and you can send it the developers, and I have never taken the time to try to figure out what any of that stuff is because I am not gonna be able to fix whatever it is and so I’m not gonna take the time. However, in my line of work where I’m supervising a lot of file ingestion people, data, architects, and software engineers, it definitely behooves me to understand what the errors I’m seeing with our own in-house proprietary products are. It’s especially frustrating when some of the higher up software engineers want to exclude me from meetings about the products going down because they claim it’s too technical for me. It’s not, of course, it’s not even the real reason; they just want to exclude me because they’re afraid of sharing their weaknesses or something. I have completely figured out what they are worried about yet, but it’s maddening.