-
When you're building a business you can try to put in plave the right architecture and work things as you grow.
I think Twitter had a decent software architecture already, and (presumably) was more or less appropriately sized for it. Details of it are asked at interview questions. I don't imagine there's be a tonne of mileage in trying to refactor it too heavily.
It's the world cup next week - I've read that some critical teams ('serve tweets' being one of them) now have no employees. I imagine there's a really high risk that twitter will go down sooner rather than later.
-
software architecture
Sorry I meant architecture in a wholistic sense - all the systems, processes, organisation, etc. and businesses generally.
But yeah the general point stands. Although I guess it would be interesting to do a compare and contrast with some old school case studies - as I can imagine there are some similarities between the "excesses" in modern tech cos compared to companies of the past with final salary pension schemes and strong unions.
The very best will have jumped at the time of purchase so they could get the prime jobs elsewhere, before the rest started leaving.
The other issue is it's an established company so retaining knowledge is usually really important.
When you're building a business you can try to put in plave the right architecture and work things as you grow. With an established one you've got so much legacy stuff that even if there are issues with it, to start you need people who know what they're doing.