Called it. Elon’s doing exactly what I thought he would do: https://aus.social/@ajsadauskas/109979152813584947

Twitter is dead.

There is no point in trying to hold on to what Twitter used to be. What Twitter used to be no longer exists.

It died the moment Elon walked in the building.

Anything posted there since then has been free content on his everything app and potential crypto scam, X: https://www.theguardian.com/technology/2023/jul/23/twitter-elon-musk-says-he-wants-to-change-companys-bird-logo

#Twitter #Elon #ElonMusk #Fediverse @technology

  • @[email protected]
    link
    fedilink
    59
    edit-2
    11 months ago

    His utter lack of understanding about how SAaS companies work is astounding. Having worked on the backend of several, they’re all hot garbage and brittle. That’s why there were so many “useless” engineers. You know, the ones he shit canned when he acquired the company? Surprise, they were probably the only reason the dumpster fire wasn’t burning down the whole city block. The thing Elon fails to understand is that someone didn’t just write Twitter on one go and gift it on to the world. It has evolved over many many years. Technology stacks change, frameworks change, standards change and these companies are trying to continually add features to applications and don’t have the luxury of just rewriting the whole stack every time something new comes out. The end result is something that is often more akin to a living organism than a website or application. He probably thinks Twitter is some program running on every server that can just be rewritten and replaced. I can’t wait for the day they try to replace it and it ends up setting Twitter back a decade.

    • @[email protected]
      link
      fedilink
      611 months ago

      The thing Elon fails to understand is that someone didn’t just write Twitter on one go and gift it on to the world.

      He did actually say at once point about scraping all the code base & starting from scratch!

      • @[email protected]
        link
        fedilink
        411 months ago

        Software Developer pro tip: Never ever get involved in any effort to rebuild the old system in new tech.

        Make a new, smaller system to take new market instead of the old system? Good.

        Suffer for years through an endlessly growing checklist of things that must be in this new thing because they were in the old thing? Arguing with sales whether you have to again rush out a fix for a customer that is important and absolutely depend on this integration with Microsoft Bob that nobody in the dev team even knew existed in the old system until the customer complained? Have release schedules set years in advance and constantly pushed because this thing will never ever ever be accepted as a replacement of the old system? Bad.