|
|
|
|
|
by matrix_overload
897 days ago
|
|
People fundamentally misunderstand how this works. For a large enough product company there's always a years-long queue of feature requests, fixes, optimizations, and other things to do. All of it will never get done! The doable amount of highest-priority items will get picked through a combination of pressures from different people and departments, and will get more or less implemented. If you cut the workforce by 50%, instead of doing 30% of the infinitely growing backlog, you'll do 15%. Since most of the completed work gets obsoleted or thrown away due to various inefficiencies, there will be some effect, but it will be far from dramatic. As for the individual workload, you'll carry as much as you let the company put on your back. And that mostly depends on your negotiating skill, and somewhat on the supply/demand dynamics of the current labour market. The latter will tough for the couple of years, but the former is up to you to level up. |
|
I've never seen a layoff actually care about what team they're removing from when it comes to ENG.
In this case it's probably 500 across twitch, which for some teams is going to be devastating.