• jamesoh5
    link
    fedilink
    English
    arrow-up
    148
    ·
    3 years 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
      75
      ·
      3 years 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
        link
        fedilink
        English
        arrow-up
        34
        ·
        3 years 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.

      • rewmiedeleted by creator
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 years ago

        deleted by creator

      • tox_solid
        link
        fedilink
        English
        arrow-up
        46
        arrow-down
        1
        ·
        3 years ago

        Former individual is just the politically correct way to say dead guy.

        • SJ_Zero@lemmy.fbxl.netdeleted by creator
          link
          fedilink
          English
          arrow-up
          21
          arrow-down
          1
          ·
          3 years ago

          Actually, he pissed of Captain Janeway and was erased from the timeline.

          Used to be a nice guy before he became a former individual.

      • qisopedeleted by creator
        link
        fedilink
        English
        arrow-up
        14
        ·
        edit-2
        3 months ago

        deleted by creator

    • NotMartyMcFly
      link
      fedilink
      English
      arrow-up
      34
      ·
      3 years ago

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

      • teuast
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        11
        ·
        3 years ago

        A day that will live in Internet infamy.

    • root
      link
      fedilink
      English
      arrow-up
      28
      arrow-down
      7
      ·
      3 years 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
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      9
      ·
      3 years 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.

    • Sunrosa
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      I’ve noticed that my batch image downloader works on maybe 40% of all twitter posts, and only 40% of the time (It used to work 100% of the time before Musk arrived). It’s fucking annoying. I think they’re having major API and CDN issues.

    • root
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      15
      ·
      3 years 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
        ·
        3 years 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.

        • Saneless
          link
          fedilink
          English
          arrow-up
          27
          ·
          3 years ago

          I’ve heard this multiple times from the same person even

          • teuast
            link
            fedilink
            English
            arrow-up
            17
            arrow-down
            12
            ·
            3 years ago

            wow me too, what are the odds

            • ricdeh
              link
              fedilink
              English
              arrow-up
              7
              ·
              3 years ago

              That’s just what I’ve heard!

    • root
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      19
      ·
      3 years 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
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      17
      ·
      3 years 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
        link
        fedilink
        English
        arrow-up
        7
        ·
        3 years 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.