I hear you loud and clear, especially the part about which university to attend, to even make sense of Analytics. But when it comes to bad UX and UI, I believe Microsoft takes the prize for the worst offender. And the most costly to society - we have now spent 7 months trying to learn enough about Microsoft's stack to produce a fairly simple app for Microsoft Teams. And we've been developing software apps for >40 years, so it's not that we lack knowledge on how to do this.
You said, you get it; you understand that Google is an engineering company and thus it had some excuse for poor UI's about 10 years ago. Ditto for Microsoft, and yes they are innovating, but they are still not giving one tiny thought to UX. And as such they are costing every developer out there, countless hours of wasted effort. MS's documentation is either too high a level, aimed at introducing the topic, or is precisely the detail on the feature I am looking for, but is hopelessly out of date and refers to buttons and functions which are not visible in the UI in front of me. And if you're thinking, just submit a support ticket, it took 7 support calls to find the app I had been given the licence keys to (Dynamics 365) as part of our Developer agreement, because the first 6 people behaved just like me: if you're handed the keys in one admin portal, surely that's where the app will be available from! No, not in MS Land - You get the keys in Partner Central; you activate the app in PowerApps Admin Portal, you provision it or manage its data in Admin365 Portal, and you edit or modify it using the PowerBI portal and not once does it tell you any of this, anywhere. How's that for a totally fucked UX and when I try to point out that life would be much easier if there was just one place to administer the app from, it's like I'm speaking a foreign language. And again, as you said about Google, Microsoft is awash in money these days. They could fix all this in the same way Google could. But they don't give a shit.
And, I guess being fair, many of the apps I have to use these days appear to suffer from the same issues. They do the function they were designed for, but they do it without regard for the way the user is trying to use the app to do his or her job function. It blows me away that anyone would develop an app for a function without knowing how that function is used in real life - truly a precise recipe for a horrible user experience. But it does seem that people like you and me are becoming more and more rare.