Twitter's high ROI engineering work(twitter.com) |
Twitter's high ROI engineering work(twitter.com) |
slow clap
As best I understand the Twitter spat, he was claiming the client was making 1000 RPCs to generate the home timeline - hence it being slower in India where mobile internet is slower. Except the Android dev pointed out it was actually only 6 (IIRC) calls from the client and slowness had nothing to do with that.
Upon closer inspection, they’re full of s*t
Revenue and user growth and product stagnated. So who cares about optimizing a further 100ms improvement or what OSS they maintained?
The “interesting stuff” you see in this post is what many engineers love to do. Make work for the sake of work. It doesn’t always translate into growth.
> The Apple product has not meaningfully changed or evolved in 10 years
> The WhatsApp product has not meaningfully changed or evolved in 10 years
Twitter’s workforce bloat has outpaced both its users, revenue, and its share price.
In the last few years alone they made huge changes like Blue, reader mode, ad-free articles, super follows, birdwatch, spaces/ticketed spaces, the list goes on.
[1] https://edition.cnn.com/2022/11/11/tech/musk-twitter-ftc/ind...