• jamesoh5@lemmy.world
    link
    fedilink
    English
    arrow-up
    151
    ·
    1 year ago

    As a former individual who understands the underlying systems, it seems like they botched deployment of a new feature causing issues and cannot figure out how to solve them.

    Most of Twitter is and has been in maintenance mode since acquisition (think of 10 man engineering team and 1 left to handle maintenance).

    • Quacksalber@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      74
      arrow-down
      1
      ·
      1 year ago

      This is why it cracks me up every time when someone is praising Elon for “cutting slack” when firing all those twitter employees. Yes, twitter did not implode immediately. Turns out, people can build software that is stable enough to run in maintenance mode. But good luck dealing with new issues cropping up.

      • KairuByte@lemmy.world
        link
        fedilink
        English
        arrow-up
        34
        ·
        1 year ago

        People too far removed from IT/Dev team can become disillusioned as to what they do.

        If you have a good dev team, you won’t hear about them doing anything until shit hits the fan. If you haven’t heard from them?… They’re doing their job. Leave them alone.

    • NotMartyMcFly@lemmy.world
      link
      fedilink
      English
      arrow-up
      33
      ·
      1 year ago

      From what I read they refused to pay Google for hosting services when the contract was up for renewal…which was June 30th.

    • root@lemmy.world
      link
      fedilink
      English
      arrow-up
      27
      arrow-down
      6
      ·
      1 year ago

      I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.

      This is just what I’ve heard.

    • root@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      9
      ·
      1 year ago

      I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.

      This is just what I’ve heard.

    • root@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      14
      ·
      1 year ago

      I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.

      This is just what I’ve heard.

      • jb007gd@lemmy.one
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        7
        ·
        1 year ago

        I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.

        This is just what I’ve heard.

    • root@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      19
      ·
      1 year ago

      I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.

      This is just what I’ve heard.

    • root@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      17
      ·
      1 year ago

      I heard similar; That this was the result of a migration away from Googles storage, which was cut off before they had the replacement fully set up. So they lost a ton of data and are severely limited in what they can display.

      This is just what I’ve heard.

      • jamesoh5@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        It’s not a result of Google storage. Google served only for data analysis and batch jobs. These would not be sufficient enough to cause service degradation. Just a bad launch of a feature (via server side) that had unintended consequences.