This is just the latest in a series of vibe-coding caused bugs, Spotify famously claimed their best devs were no longer writing any of their own code:
https://techcrunch.com/2026/02/12/spotify-says-its-best-deve...
I don't understand enterprises who take this stance, there is tons of room between "don't utilize AI for coding" and "exclusively utilize AI for coding."
Spotify has always been garbage software long before LLMs. PM/devs like to justify their constant a/b testing to gamify metrics to curry raises/promotions but for end users all we're dealt with is a constantly broken/changing UI.
My biggest peeve with Spotify UI is how hard it is to add something to your current playing queue, an action I would assume is quite common but you have to scroll down to hit several controls before you can do it.
Don't you just swipe right on a song to add it to the queue?
Three dots next to the song title, menu opens, "Add to Queue", done.
Keep doing. Hearing people complain about streaming software, when they could be playing their sounds locally with free software, makes my day every day.
Try using apple music
I bought another app to play Apple Music because that’s how much the Music app usability has decreased.
It's fully caused by management mindset. There are companies that are investing hard on the AI trend, but the message is clear: all code pushed is your ultimate responsonsibility, and if it lacks quality or causes problems, you're on the hook for it; using AI hasn't changed that.
So if Spotify had a modicum of AI usage hygiene, plus accountability expectations for code quality, this would still mean a bad performance review for whoever introduced this issue (person or team; poor results and mistakes are never something that come from a single source)
> Spotify famously claimed their best devs were no longer writing any of their own code:
It seems almost criminal to hire Ludvig Strigeus and then not let him write code.