3 ms·
This approach doesn't make sense when it comes to software. Expanding your dev team during a boom year to only contract it in the future bust year - will leave
by lumost 4y ago
This approach doesn't make sense when it comes to software. Expanding your dev team during a boom year to only contract it in the future bust year - will leave you moving slower in the bust years. While tech has never been known for it's stable job market, seeing the most profitable corporations in the world conducting layoffs doesn't sit well.
- UncleMeat 4y agoNot only that, but layoffs are not precise. People on my team were fired today. They weren't my lowest performers.
- riku_iki 4y agoany idea what was the selection criteria?
- UncleMeat 4y agoNo. We are still finalizing annual reviews. It couldn't have been current performance ratings. I know of some low performers on nearby teams who weren't laid off. Some (many?) teams were entirely unaffected, so somebody up in my management chain decided my team was less critical. No clue how the individual people decisions were made.
- bumby 4y ago>will leave you moving slower in the bust years How is this any different than any other industry? In manufacturing, slowing reduces the risk that supply will outstrip demand. In software, slowing down means reducing the risk that time is spent producing software that won't have an economic payoff. The effort is focused on the business lines that add to the bottom line and less on the speculative ones. If you look at where a lot of the tech industry layoffs are coming from, they tend to be the not-yet-viable moonshot ideas.
- lumost 4y agoImagine you had a factory. During the boom years you hire extra engineers to improve the factory. These engineers busy themselves adding new production lines and creating more complex manufacturing processes to support products. 2 years later you sack the engineers. You are left with more complex product and extra assembly lines. You aren’t sure which ones you need or are obligated to continue - so you run them all.
- bumby 4y agoIs this meant to be an analogy for software production? It seems like the crux is here: You aren’t sure which ones you need or are obligated to continue This is essentially saying leaders/managers don't know how to prioritize. What much of tech is doing right now is prioritizing by cutting back on the programs that aren't particularly successful. It's the same thing done in manufacturing.
- horns4lyfe 4y agoThis is such a bean-counter MBA perspective. It’s tech, if you want real growth, you need moonshot ideas. If you want to just become a GE style dependable divided stock, then fine, but your shareholders aren’t going to triple their wealth again.
- bumby 4y agoNobody is saying reduce moonshot ideas to zero. There's a difference between "throwing everything at the wall to see what sticks" to having a risk/reward way of prioritizing what to fund. What you're alluding to is the "grow at all costs and find a way to be profitable later" strategy that is prevalent in SV, but tends to not work so well in real economic downturns. Sometimes I think people either forget, or are too young, to remember that the pre-2021 decade+ of near-zero interest rates are a historical anomaly. Put differently, take a look at the R&D costs of google[1]. Note how, despite a constantly increasing amount of investment, they still derive 80% of their revenue from ads. Granted, some of the R&D will contribute to ads revenue, but it may also be indicative of a moonshot strategy that isn't contributing much in terms of "real growth" in alternative revenue streams. [1] https://www.statista.com/statistics/507858/alphabet-google-rd-costs/ https://www.statista.com/statistics/507858/alphabet-google-r...