is this microsofts way of saying more layoffs are coming?

@Viss This includes availability, right? They will take a look at how many ppl can't use Teams at any given time, right??

for literally years now, I've heard basically this, from staff in or adjacent to MSRC:

"we find bugs, customers find bugs. those bugs get reported up stream to the devs, and the devs basically tell us to get stuffed, they dont care, and they arent going to fix the bugs."

so...
are we now to believe that those devs in question are going to be shot into the sun?

I'll believe it when i see it.

@buherator good question

@Viss in a work environment where bug fixes aren't valued, it's not in any dev's best interest to proactively do any. Fixing bugs means less time shipping new code. Surely this is one contributing factor to enshittification.

I say this as someone who was fired for focusing on glue work, because nobody else on my team was doing it. And it was noted that nobody did it after I left.

I've heard of a big tech company (not MSFT) where you'd be punished for writing up a bug report if you didn't already have the solution prepared. I think about that a lot.

@giflian this just screams of leadership with zero foresight

see what i mean

@Viss Yeah this whole situation is just sad and busted. Defenders are at likely the most asymmetrically vulnerable state they've ever been in. At least in previous perilious situations, they were more aware of the asymmetry. Now vendors are actively hiding problems.

I’m morally in support of coordinated vulnerability disclosure, but the bad actors are on both the adversary side and vendor side, now. It may be time for researchers to let loose the vuln cannons for a bit.