3 ms·
There's a huge difference between "caring" and acting effectively. If the CEO is letting the company get bloated in better economic conditions and self-destruct
by lapcat 4y ago
There's a huge difference between "caring" and acting effectively. If the CEO is letting the company get bloated in better economic conditions and self-destructively slashing in worse economic conditions, who cares whether they "care"? One might say that the CEO in both of these cases is merely reactive and not proactive. Anyone can follow the winds as they shift.
Also, "the economy" is merely an aggregate, an abstraction. In every economy there are both winners and losers. People tend to forget that one of the most successful products in history, the iPhone, was introduced shortly before the so-called "Great Recession". Of course a lot of workers and consumers were hurting during that time, but apparently there were still plenty of people able to afford new iPhones too. Imagine if Apple had decided to cut back severely rather than investing; that would have been a huge mistake. If you believe in your product, then you need to stick with it.
- cptaj 4y agoI think I can put this duality in developer terms. Technical debt. When you're growing fast, you accrue technical debt because you prioritize milestones over quality. The same goes for the hiring process. You might need a big push for some deliverable so you hire more people. After that, you're stuck with the people and whatever structural growth your company went through. Then on the software side, the project gets bloated and grids to a halt so some asshole proposes a refactor in rust. This is largely useless and will further complicate things. Same can happen for layoffs in bloated company. You wanted to streamline but you ended up disrupting the processes you had and losing talent, which leads you to bad performance and rehiring.
- SkipperCat 4y agoSound like laying off the person who wants to refactor in Rust would be a win-win.
- version_five 4y agoI thought that went without saying
- karmakaze 4y agoOT: Pet peeve 'refactor' is not synonymous with arbitrary (or even deduplicating) change to source code. It's to consciously choose a (different) factor to separate out and allow seams to form around. People who use 'refactor' too generically are often focused more on the form of solution than the problems themselves.
- bombcar 4y agoAlso if you try to enact layoffs during the “boom times” every single manager will be demanding a “special case” for their team - a big headache. If everyone’s doing it in crunch times, the internal pushback is much less.