• shrugs@piefed.social
    link
    fedilink
    English
    arrow-up
    112
    ·
    edit-2
    4 days ago

    i like that the explanation sounds like nobody is able to review the code and find / fix the bug.

    Either someones on vacation or Gemini is still trying to vibecode a solution

    • comador @lemmy.world
      link
      fedilink
      English
      arrow-up
      61
      ·
      4 days ago

      If I were forced to pick, I’d say it was caused by an inexperienced programmer using AI that caused this.

      • floofloof@lemmy.ca
        link
        fedilink
        English
        arrow-up
        20
        ·
        4 days ago

        It’s never just the developer that’s the problem. There should be a system in place to catch obvious bugs like this before they get anywhere near production. So there’s something not right in the company’s review and testing practices. And a bug like this, if it does sneak through, should be fixed very quickly. This has been up for a while so again there’s a problem with the company’s processes.

    • rozodru@piefed.world
      link
      fedilink
      English
      arrow-up
      18
      ·
      4 days ago

      the fact this thing has apparently been happening for a week or more is weird. It’s like front end web dev 101 type stuff and the fix is quite simple a junior should be able to take care of it. So I’m leaning towards it was an AI “assisted” bug and none of the vibe coders know how to fix it OR what’s more concerning to me is they no longer have any qualified front end devs on staff to fix it. you can literally fix this thing via your browsers dev tools right now if you wanted to.

      but yeah if you start looking at the youtube front end you’ll quickly see it’s all pretty much vibe coded now. Another clear as day tell on that is the subscribed shorts section. it’s been broken for months and the fix is easy, they just don’t know how to do it.