Anyone with a cursory knowledge of warren knows her lengthy history with advocating for consumer rights. I mean, you seem to be trolling and engaging in bad faith. A look at a Wikipedia page would suggest your initial comment was ludicrous.
I arrived at work at msft nearly every day by 730 for the first five years. By the end of year six I was puking in the garage thrice weekly at 9 am due to years of chronic stress, lack of sleep, and caffeine use. It’s taken me about a year, lots of medication, and CBT to get back to being able to sleep regularly for over 6 hours.
I mostly view this as the turn from SDET to Quality. SDET used to do both telemetry and quality testing, coordinating with devs frequently. Now Quality mostly coordinates with PMs. Satya as Azure head had success via this method, so it's copied throughout the entire company
my mother's 401k at the time, they were forced to buy company stock. Her company was also in the process of merging with Enron. Luckily, my father had a better plan so they ended up mostly investing in his and what was left over they invested in hers.
Wand is great. Thought their latest album was from a different band because it's so different than the random freebie I got from my local record store (their Golem record, it was bent)
They erased the Software Developer in Test role, and moved to a 'Quality' role.
The 'Quality' role implements Telemetry for the working product which turns into metrics that PMs/Dev Managers look at to determine shipping.
I used to be an SDET, and re-interviewed in order to be a Dev after the big switch. I could have rolled right into 'Quality', but I didn't find that as interesting. As a result, the automated Testing that used to be done by the SDET team is moved to be the responsibility of the Dev teams. Most dev teams knew little to nothing about the automated tests that were being run every day against their code (Upgrade tests, BVTs, integration tests).
SDETs also created tools and internal frameworks which were created to reduce cost; for example, I implemented a Code-Coverage based test-pass to reduce the 24 hour automated test suite that was running every day on Windows Phone main branch.
The previous SDET role's responsbility has moved 100% to Dev Teams, none of which had to ever think about that facet of development before. As a result, you get me implementing automated test suites for 5 different teams in 3 years (WSL, Ink, Text, Touch input, kernel sec) because I know the frameworks more than 25 year veterans of Windows internal development. Some of these teams had 10-15 years of built in collatoral that is now attempting to be revived because management realizes that they've dropped the ball quite a bit.
biggest negative I would say is getting rid of the SDET role and moving them into Telemetry.
It moved the onus of testing on Devs who've never done it before as part of their job and thusly very lacking. The bungled W10 recent releases can be directly tied back to this model. As PMs and Devs don't account for testing like they used to before shipping to customers.
This may be fine and dandy short-term, but if you're biggest customers rely on stability for code bases over 25 years old--getting rid of focused testing and reliability is a big no-no.
Most of the initiatives Satya has gotten credit for were started under Ballmer. Some of the worst moves I've seen regarding current MSFT internal culture were direct results of Satya
Source: Me, at MSFT before Ballmer left and still there now.
That doesn't mean Satya's not had a good effect overall. Part of the investor postives were due to PR differences that Satya made (which are very good), and his ability to talk about the future of the company is far superior to Ballmer.