Shaggar posted:

twitter almost certainly had and continues to have more people than it should need, but the problem is they went in on microservices and growth which leads to spaghetti code where you need like 10x the people to maintain it. if they had approached it with a more traditional design they probably wouldnt be able to add features that nobody uses every 5 minutes, but they'd need way less staff and it would probably perform a lot better.