People dramatically underestimate (or are outright unaware of) the effect of Elon's takeover of twitter had on the tech industry. Twitter needed to collapse, so everyone would see what firing 80% of the workers would do to a tech company.
Trying to keep alive 30yr old tech stacks and still pass security reviews, while doing stuff like manually compiling and packaging python 2 and jre6 tools. Ouch.
I've taken money to create software for most of three decades and I don't think I've ever actually worked on software that needed the people who created it to be near it while it was running, once it was working.
I think the record single instance uptime on a customer site was most of a decade, running a TV station.
They don't - not the same way that farms or factories need laborers. Some small fraction of your software workers need to be around to handle the running software and hardware in case of failure. In the context of union bargaining power, the difference is important.
If the factory workers don't show up for work, your factory's output immediately drops to 0%. If none of your software engineers show up, most of your company's code will continue to run, some of it in a degraded state, for a while. (How much depends on your sub-industry, and how much you're outsourcing to AWS). And if you can get 5% of your workers to show up, you might be able to handle 90% of the on-call load.
They cut quite a lot projects and side products (from tweet deck to different statistics and insights to ads), some other things they scaled down a lot (in the past one could read everything without being signed in, now they limit to sign in users, which certainly takes a lot of load and thus need to keep systems running)
Looking at Twitter's valuation, revenue, user count, uptime, new feature launches and really any other metric since the big layoff I wouldn't exactly consider the company thriving.
The claim isn’t that they’re thriving. It’s that it works. I’m not sure on any figures since it isn’t a public company. Where are you getting your numbers?
Losing devs that built a service, its infrastructure, build pipelines, tests, etc. Can sometimes mean losing deep knowledge.
Sometimes an issue arises and without that deep knowledge you'll be waiting weeks for a fix. Better hope it isnt a critical issue like a serious vulnerability or that you can hire the deep knowledge on a temporary consultancy contract.
Sometimes services are fully rewritten from scratch because the new devs cant get a build of the old service to compile/run/do the thing™.
Staring down the barrel of being primary on-call over Christmas for a dozen k8s clusters running thousands of nodes. How I wish it were true that we could trust computer programs to just keep running.
If your work place has a long enough history, try comparing incidents on work days versus weekends or holidays. Typically the incident rate is dramatically lower when no one is making changes.
Totally true, but we host other people's code (PaaS, etc). We don't get to dictate their working hours.
It also doesn't mean nothing breaks when people aren't making changes. Certificate expiration is the classic example of something breaking _because_ someone hasn't made a change. Or a slow memory leak. There's a whole classification of issues that get worse when nothing is redeployed for long enough.
You do realize that, um, software need hardware. And also security upgrades often require software engineers. And uh, software maintenance is what engineers actually do most of the time.
It only takes one bad deployment to bring huge swaths of the internet down nowadays, just look at Cloudflare, AWS, etc. costing millions of dollars in downstream economic impact.
Sure, a platform will continue to run on a given day without intervention, but that’s like playing Russian roulette: at some point you’ll need intervention and you’ll likely need it fast.
There's not really an equivalent with most service industries. Software engineers don't even need to be around for the programs to keep running.