• iByteABit [he/him]
    link
    fedilink
    arrow-up
    33
    arrow-down
    1
    ·
    1 year ago

    How did this even pass to production, do they just merge shit to main and pray to God it works?

    • dustyData@lemmy.world
      link
      fedilink
      arrow-up
      41
      ·
      edit-2
      1 year ago

      Whenever you see this sort of technical problems from Twitter. Remember that Musk fired almost all of his staff. Including software engineers.

      • BURN@lemmy.world
        link
        fedilink
        arrow-up
        20
        ·
        1 year ago

        And the ones he didn’t fire left en mass. At least the ones not tied down by visas and/or other red tape

          • BURN@lemmy.world
            link
            fedilink
            arrow-up
            6
            ·
            1 year ago

            I am one of those lazy ass office workers lol. I’m sitting here at work on Lemmy, but even I would have been jumping off that sinking ship a long while ago.

    • Katana314@lemmy.world
      link
      fedilink
      arrow-up
      15
      ·
      1 year ago

      When I think about it, this is actually exactly the kind of bug that very easily passes to production.

      You have your dev environment; something like “katanasdevmachine.twitterdev.com”, where you do your work and verify bugs. This environment is configured with a developer database, and developer URL configurations. So there might be “katanasdevmachine.twitterdev.com” simulating x.com, and then “briansdevmachine.twitterdev.com” to represent twitter.com. You and Brian do a test of the redirect from there, and all’s well.

      It’s only when you’re moving to the genuine domains that small URL-parsing/concatenating bugs might show up. But there’s not many easy ways to “simulate” being on the actual twitter.com website with test code you’ve written. It’s doable, just not convenient. So, these sort of URL configs can very often be the one place that bugs essentially go “untested” in an imperfect workflow.

      • bronzle@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I mean, /etc/hosts, but I see your point. I’d guess this might be a case of, “this is pretty simple, we’re good to go”. then “oops”