Microsoft has yet to explain how or why the lapse occurred.
Highly skilled technical staff are expensive, and it turns out that some people still use Windows when Microsoft doesn’t hire the talent necessary to keep Windows working.
Edit: Also, bribes from three letter government agencies are probably pretty nice.
It used to be Microsoft would hire the best and brightest people straight out of university. Most of those people went in thinking they were going to fix the problems. Usually management would grind them down and they’d give up and go work elsewhere. But they did have some talented people and occasionally those people would be able to make improvements.
Microsoft always sucked, but occasionally they could put out something good. There was a lot of inertia and a lot of half steps backwards for every step forward kind of thing going on. Mostly treading water, occasionally improving.
But now they’ve gotten rid of a lot of people so they can throw more money into the AI money pit. Microsoft is in a constant decline now. The people that worked there that would fight the good fight to improve things (and every now and then win a fight) probably aren’t there any more.
Holy hell yes. It’s actually alarming how many security holes are out there simply because management had no clue what people did and canned the last guy responsible for maintaining something. Zombie functions that are holding up the whole stack, but no one has had a clue what they did in 15 years, and we all just look away and hope they keep holding until they’re someone else’s problem.
I cannot make certain teams at my work give a shit about known security vulnerabilities in libraries they use, since they don’t trip our internal scanners. People have their own priorities. ¯\_(ツ)_/¯
Highly skilled technical staff are expensive, and it turns out that some people still use Windows when Microsoft doesn’t hire the talent necessary to keep Windows working.
Edit: Also, bribes from three letter government agencies are probably pretty nice.
It used to be Microsoft would hire the best and brightest people straight out of university. Most of those people went in thinking they were going to fix the problems. Usually management would grind them down and they’d give up and go work elsewhere. But they did have some talented people and occasionally those people would be able to make improvements.
Microsoft always sucked, but occasionally they could put out something good. There was a lot of inertia and a lot of half steps backwards for every step forward kind of thing going on. Mostly treading water, occasionally improving.
But now they’ve gotten rid of a lot of people so they can throw more money into the AI money pit. Microsoft is in a constant decline now. The people that worked there that would fight the good fight to improve things (and every now and then win a fight) probably aren’t there any more.
The number of times I’ve seen a fix not get pushed because somebody got laid off is a lot higher than you might think.
Holy hell yes. It’s actually alarming how many security holes are out there simply because management had no clue what people did and canned the last guy responsible for maintaining something. Zombie functions that are holding up the whole stack, but no one has had a clue what they did in 15 years, and we all just look away and hope they keep holding until they’re someone else’s problem.
I cannot make certain teams at my work give a shit about known security vulnerabilities in libraries they use, since they don’t trip our internal scanners. People have their own priorities. ¯\_(ツ)_/¯