If i was one of those actually productive "star engineers" at twitter who was actually delivering, and it was clearly communicated that the layoffs are targetin

If i was one of those actually productive "star engineers" at twitter who was actually delivering, and it was clearly communicated that the layoffs are targeting the absolute deadweight, I would honestly be delighted to stay. Out of all the dev jobs I worked, I was much happier at places where the deadweight engineers weren't making up a giant chunk. Because not only it is a bit demoralizing to work in that environment, all the prioritization and incentives for the deliverables get screwed up for me as well. I get that my previous statement was a bit vague, so let me elaborate. New features, timelines, approaches, etc., they all get prioritized and decided based on what the heavy majority of the devs and managers feel is important. Oh, and managers take into the account what their devs want too, to a degree. At this point, you probably realize that the whole situation turns into a tyrrany by the deadweight majority. No, I don't want to do another refactor of a perfectly good codebase just because someone wants to do some pretense work for a few hours a day, especially since we have already done a major refactor/rewrite not that long ago. Doubly so when reasons for it cannot be articulated with anything but a buzzword soup that makes zero sense anywhere outside of the performance review.