[arrrg]

Your reference to prompting is pretty disgusting since you try to shift the blame to the user. All the prompts were crystal clear. Trying to shift any blame on user error is non-sensical stupidity or dumb manipulation in this case.

Also, might I recommend looking at the way the world is, not the way the world might be. This is one of the ugly AI tendrils this disgusting industry is putting into everything, bringing ruin to the world. This is the actual reality of it, making the world a dumber, less interesting more stupid place.

[Closi]

> Your reference to prompting is pretty disgusting since you try to shift the blame to the user.

I'm shifting 'blame' to Spotify, rather than the user or the AI model - although blame is probably a pretty strong word anyway for what is probably just supposed to be a fun DJ feature.

> All the prompts were crystal clear.

We don't know what the prompt is, because the FULL prompt will be a combination of the base prompt plus the user prompt. It's trivial to show that a modern model with a minimal base prompt will return correctly (as per my original post), so IMO there is probably something in the base prompt which is encouraging the model to return differently.

I wanted to clarify the first two points, but i'll not respond to the rest of your comment as it's a bit overly-emotive (calling what I say disgusting, rambling about the downfall of society as a whole etc).

[foltik]

Pretty sure they were saying it was a skill issue on the part of the Spotify engineers writing the internal system prompt for their slop DJ.

[phony-account]

> it was a skill issue on the part of the Spotify engineers writing the internal system prompt for their slop DJ

Spotify are currently making a big deal about not writing any code - I attended a webinar this week where one of the slides proudly trumpeted this fact:

“ 0 lines of code

Spotify's best engineers have not written a line of code since December.”

[criddell]

December? I would have guessed it’s been longer than that.

[foltik]

A full decade since spotify wrapped was released and we still have the grand unified … menu with a seemingly randomized list of actions that takes hundreds of milliseconds to load depending on network conditions. And buggy jams that desync constantly. And it’s way too easy to accidentally clear the entire queue. I could go on, wonder what the hundreds of PMs are doing?

Bunch of clowns coasting on their moat instead of building an actually good product.

[joegibbs]

"Disgusting" is a strong term to use regarding a poor quality music chooser

[mikkupikku]

> Your reference to prompting is pretty disgusting since you try to shift the blame to the user

Users are often to blame in many varied cases and there should be no taboo around discussing this. I think maybe some people hear that you should never blame rape victims for rape and then go running wild trying to apply that as a general principle of never blaming anybody who is in any way a victim of anything, even when the "victimhood" is simply some piece of trivial software not working well. But we're not talking about rape so your intense rejection ("disgusting") is completely off the mark.