> Everyone said Twitter would have crashed and burned by now. Nobody said that![0] I'll have to trot out my code-freeze analogy again: a lot of companies succe

> Everyone said Twitter would have crashed and burned by now. Nobody said that![0] I'll have to trot out my code-freeze analogy again: a lot of companies successfully perform code-freezes and run with skeleton crews when a lot of staff are away (think end of year holiday period in the west, and the Chinese new year in China). Nothing crashes and burns, because that's the period of lowest entropy, and the periods are brief. Things get shaky when changes are made, and you run into unexpected first and second order effects. That said, my Twitter experience is already degraded: some tweets don't always load on the first try ("Tweet is unavailable" which I had never seen before the Musk era, except for legitimately deleted tweets[1]). I've also started seeing a scrolling bug in the mobile app, where it twitches endlessly, until I nudge it a little more. I've ended up turning off auto-updates to avoid new UI bugs. The web client has terrible layout on mobile (when I last checked), where some UI elements didn't fit on the screen horizontally. It's a death by a thousand cuts 0. That which can be asserted without evidence, can be dismissed without evidence. 1. I'm assuming there is an elevated error rate somewhere in the bowels of Twitter as some client requests fail for some seemingly random reason