No it doesn't, it actually makes my point.
My estimate was based was an estimate for how many people you would need for a twitter company.
Twitter had 8000 employees, it will have procedures and approaches assuming all those people exist.
For example
The first step when DevSecOps consulting is to document the processes a team is following. Then you can automate those processes.
Inevitably there will be a step that is very laborious (typically produce a report/metrics). You start asking if it can be adjusted and no one seems to own it.
Eventually you realise the step was for someone who has since left the company or a role that was removed several reorganizations ago.
Firing half your workforce is going to create those sorts of problems everywhere, all at once. The fact everything largely kept working despite that supports my argument.
stevecrox@kbin.run 7 months ago
Uhh how?
The rate of new features/changes is far higher, uptime went through a bumpy transition but is back to normal. From an engineering perspective it supports my point.
Twitters issues are Elon scaring away advertisers/annoying governments/content creators through his hard line on free speech allowing an explosion in hate speech.