CIRCLE WITH A DOT

@carnage4life Quite ironically when that happened our org also _added_ a new VP in the reporting chain as well (making 4 VPs to satya then vs 3 before, so ICs were actually the same distance).

@carnage4life This is more or less what happened to (my team at) Microsoft last June and July (2025).
- Lead role eliminated, only Managers remain
- Team sizes 11-13
- Many most junior/recent hires laid off
- Many _very_ senior leads laid off
- Our group lost 50% by count for instance
- Any leads that remain were told to be “tech lead” or “player coach” (depending on team) — I argued that at principal levels, their role involved coaching and influence regardless, labels didn’t help.

@dandean Agreed. In my time, I’ve always just used “dev” for developers. So few ever demonstrated engineering rigor. Leaders chased revenue. Individuals chased recognition and/or dopamine.

(Yes yes, not all. But most.)

@0x00string @tess I have had personal experience with msrc liberally applying rce as well.

I get their argument. Because it can be triggered by a user clicking on a link to open remote content, they classify that as rce.

Pretty much any pattern where a user can be coerced remotely will likely get an rce tag is my guess.

But it does mean that other patterns of passive listening vulnerabilities can get watered down.