this post was submitted on 04 May 2026
356 points (98.9% liked)
Technology
84354 readers
4435 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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
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.
If I were forced to pick, I'd say it was caused by an inexperienced programmer using AI that caused this.
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.
I've met a lot of really shitty developers.
Everyone's shit sometimes (and some people often), which is why you always need non-shitty processes to preempt and/or catch the mistakes.
Everyone is shit sometimes, but some developers are shit all the time. Like, surprisingly so.