Comment by alexyoung

5 days ago

I realise I’m pissing into the wind here, but I find the LLM text on the homepage and docs quite funny/ awkward.

> “Ctrl+M turns it into a tiny player that wears any classic Winamp 2 skin, spectrum analyser, equalizer, and playlist included. 2000s vibes, pixel for pixel.”

Everything is said with too much intensity, and phrasing that sounds impressive but doesn’t really mean that much. Like “wears any classic Winamp 2 skin” feels so awkward, what’s “wears”? You mean it can use it?

I feel like if you can’t be bothered to write the code, at least document it yourself and write the marketing copy so I know you understand the product. Otherwise how can I trust running it on my computer? Did the LLM generate some amazing rm -rf somewhere, or another blunder that wrecks data I might care about?

Author here.

Yes, the code is generated. Yes, the docs are generated. I agree LLM copy is annoying and will rewrite them myself.

But I built this for myself out of frustration with the official client, and I use it every day, so every bug I find is fixed immediately. I also care about bugs and PRs from other people, as you can see the amount that have been closed on the repo. The only reason I would stop maintaining this is if Spotify kills it.

I also wouldn't call this vibe coded either. Human directed and LLM generated is fairer. It's been an intense 5 days with tons of design decisions and testing on 3 platforms. I think we need a new vocabulary to distinguish it from "author doesn't care". I do.

  • > Yes, the code is generated. Yes, the docs are generated.

    > I also wouldn't call this vibe coded either.

    It's vibe-coded. Get over it.

  • > Yes, the code is generated. Yes, the docs are generated. I agree LLM copy is annoying and will rewrite them myself.

    I find this kinda funny. Fix the obvious part, better not look at the code.

  • I would use the phrase "Responsible Use of Generative AI", from https://www.debian.org/vote/2026/vote_002#texte

  • > I agree LLM copy is annoying and will rewrite them myself.

    Remember when people used to care about making a good first impression?

  • Don’t worry. Folks are entirely too concerned about the distinction between human made and LLM made. In a short handful of years, it will be incredibly rare to find something an LLM hasn’t been involved with

  • The official client is very annoying.

    I rewrite docs myself on my own projects because they read as very LLMish, there's an intermediate stage which feels slightly less bad where I ask it to remove most of the comments, especially LLM signposting ones and then "rewrite any remaining comments and docs in a dry ukgov/gds style" which makes things slighyly less worse.

  • I'm going to sound harsh here, but please don't take this as criticism of the effort, it's criticism of how it's being portrayed. The quality might for all intents be great and useful.

    > But I built this for myself out of frustration with the official client

    But you didn't build it. This is akin to me telling an intern to build me a widget and then claiming it was me who built it. Or a construction manager saying they built a skyscraper.

    Yes, the intern and the construction crew needs guidance and management, but I can't then go to the management committee and claim ownership of the effort.

    > I also wouldn't call this vibe coded either.

    You didn't write any of the code or even the documentation for that matter. You guided a code generator that relied on you to guide high level decisions but then did all the implementation on it's own. That's vibe coding.

    • This debate is irrelevant. It doesn't matter. Having the idea and the skills to dictate a stable piece of software are all that matter.

      There is no point in taking pride in typing out lines of code by hand. The entire world is moving on.

      4 replies →

    • The construction manager can’t say they built a skyscraper? In that only for someone who personally laid every brick and ran every wire?

      9 replies →

    • If I take a photo and then use GIMP to edit it, then did I take a photo or just direct my camera at something and then steer my computer to make changes to it? After all, it's not me drawing each pixel manually. It's vibe-photoed!

      1 reply →

  • >Author here.

    Not author. LLM manager, technical producer (if we're borrowing game development language), advanced AI user; not author. Authors are those whose code was used to train LLM(s) you were using while producing this fine piece of software. I'm saying this having neither positive nor negative emotions. Just clarifying.

  • I agree that "author cares" and "author doesn't care" is a very important distinction.

    But to me vibe coded is about reading/editing the code. If all your code modifications are by prompt, it is vibe coded by definition.

  • One thing I like about Spotify is the recommendations. I like to do what i call “beat digging” which is basically exploring the platform for new artists and tracks?

    Does this still have that?

  • Should add a full page click through slop warning to each page on the site. Also give credit to the LLM that made it in the "Brought to you by" section at the bottom.

Having used Claude a lot for the past four months, I get exhausted from its style. Every sentence has been buffed and polished and enhanced and it never just plainly says a thing. It's as if you have to eat every meal with every possible flavor enhancer in existence. At one point I will totally lose it if it mentions "smoke test" one more time.

It is also totally not what I want for docstrings in code or Powerpoint drafts, where consistency in language is critical.

  • Like I said in another thread, everything Claude (Code) writes sounds like it’s congratulating itself of how smart it is. While not actually being that smart.

  • I believe AI technical prose peaked with Opus 4.6. I still use it (mostly for that purpose) and I think it's legitimately great. I'm hoping they are able to reverse the trends that benchmaxxing and RLAIF have wrought on Claude's non-code output with the future models.

    • Now that the public anger is growing i really hope Anthropics next models seriously address this. Or for that matter, i hope everyone (OpenAI/etc) starts focusing on this too.

      Intelligence is important but it feels as if the LLM is only capable of conveying information while drenching it in vomit.

Interestingly enough, https://fastpotify.rocks/winamp/ shows what I dislike about LLM-generated text: From "The buttons do what they say [...]" to "[...] a different format and are not supported" is just a huge wall of text without any visual guidance.

It's as if the person writing these lines didn't care about the result. One could argue that people not caring about written documentation isn't anything new, but in the past, these documentations also had little text. So they were easier to digest. Now, we get great walls of text that are hard to read. I cannot say that I like that.

  • What sucks is that clearly the author has prompted the model somehow to generate this text, and this prompt probably contains the actual meat that the model just "expanded on" while adding it's own fluff, and if the author just shared the actual verbatim prompt instead, the documentation would be 90% shorter but also 200% more "informative per character used".

    Just share the prompt you used, regardless of how low quality or bad it is, rather than this word spaghetti of 100s of words saying basically nothing, such a waste.

    • That would actually be a reasonable thing to do with a model that is good at writing though. I'm sure if you used that method on Opus 4.6 you'd get a pretty decent result, because Claude models used to be quite good at that sort of technical synthesis. Asking a model that is bad at technical writing (e.g. Opus/Fable 5) to write your docs is a bad idea.

      1 reply →

  • It's a weird world where they put less time into writing that doc than you did reading it.

    • The sad thing is that may not be true. If you use LLMs to write docs and actually read it, you can spend far longer trying to convince the LLM to write in a sane way than to just write it yourself.

      Semi related, but i've caught myself nitpicking small things from the code of an LLM only to realize i'm putting in more work trying to convince the LLM to make the code the way i want rather than just modifying it myself lol. It's as if i'm trying to educate it in the ideal way, as if it would learn and not repeat the mistake.. but it rarely does of course.

      It seems to me that interacting with LLMs has a large pile of cognitive traps for humans.

  • I prioritized shipping over carefully crafting docs. I thought nobody would read them and they'd rather enjoy the software. I was wrong. I'll rewrite them.

    • Then, just do not add text that adds no value. Less is more.

      Documentation is first part people see when presented. I personally hate AI written text even though I do agentic engineering a lot as well. Any user facing documentation must be reviewed, if you snoozy by reading it - remove or rewrite.

      I do not care about paragraph long comments in code, because I’m not gonna read them, but I still follow my internal guideline and cut all this verbosity to level where it readable using hooks and skills.

      So basicly like you said if you care about product do not add placeholders. It’s take away first impression.

    • Fair enough. But then, how should I enjoy the software, if the documentation to its' usage is buried beyond a whole paragraph? To be clear, I do not judge the usage of AI per se. But you can instruct AI to write a clear manual. It just takes time. :)

    • I think you got a but too much negativity, from a crowd that became more easily irratated because their AI sensor became very sensitive by e.g. reviewing a lot of AI generated code and comments.

  • Not running code from someone who has so little self awareness that they publish documentation like this tbh.

    Doesn't matter if it's open source.

  • I never thought ubiquitous human-written marketing wank was any better.

    • The difference is that the marketing stuff used to be only on corporate websites. Now it's everywhere, because pretty much everybody hates writing, and the "pretty much" can be left off when the writing is a job or some other form of obligation.

> I feel like if you can’t be bothered to write the code, at least document it yourself and write the marketing copy so I know you understand the product.

Do you not understand it?

This person doesn't owe you any work. He's providing a product for free and this is a reasonable enough description of the product.

> Did the LLM generate some amazing rm -rf somewhere, or another blunder that wrecks data I might care about?

I'm pretty sure at this point hand-crafted code is more likely to contain security bugs. The mythical "rm -rf" random LLM insertion is not a real threat. Every time I see stories about this kind of issue, it's almost always preceded by basically prompt poisoning.

  • > The mythical "rm -rf" random LLM insertion is not a real threat. Every time I see stories about this kind of issue, it's almost always preceded by basically prompt poisoning.

    It is real, typically happening when dumber models (haven't personally seen any of the SOTA ones on reasonable thinking/reasoning level do this) try to clean up stuff via bash and forget to assign a variable. Things like "rm -rf sessions/$id" without double-checking $id is actually defined, would do "rm -rf sessions/" and remove the entire directory. Add in more variables in a path like "rm -rf $HOME/projects/$user/$repo/$tmpdir" and the dumb models people think they can use for local coding, promptly removes a lot more than expected.

    Not sure how people aren't already running these agents in an environment/sandbox where stuff like this wouldn't matter, locally or not, but some LLMs do truly accidentally delete stuff for people, without "prompt poisoning", I had it happen myself while testing Qwen3.8-27B (BF16) locally just a week or two ago, exactly as described above.

    • Just recently, Opus 4.8 almost deleted a bunch of important files (I caught the issue before) because it failed to consider that two-way-sync would delete files from my NAS if deleted locally.

      1 reply →

  • > This person doesn't owe you any work. He's providing a product for free

    A product being free doesn’t make it exempt from criticism. It’s not about “owing” anybody work.

    > and this is a reasonable enough description of the product.

    It’s not a great idea to signal a lack of effort, nor is it wrong for users to pick up on that signal. This is the post-llm equivalent to spelling or grammatical errors.

    > I'm pretty sure at this point hand-crafted code is more likely to contain security bugs.

    LLMs produce code which is fairly ‘locally optimal’, so in good hands they can absolutely be used to build correct software. They also allow those with little to no experience* to cobble something together very quickly and easily while creating a ton of security holes. I think you might be underestimating how common the latter is.

    * not to suggest this applies to the OP necessarily. Rather some extra wariness is necessary nowadays since the floor has been lowered so much.

    • > A product being free doesn’t make it exempt from criticism. It’s not about “owing” anybody work.

      You can criticize it but your criticism is hallow

      > It’s not a great idea to signal a lack of effort, nor is it wrong for users to pick up on that signal. This is the post-llm equivalent to spelling or grammatical errors.

      Why should you put in effort to something that should be effortless? Why should I waste my time writing some inferior copy by hand?

      > LLMs produce code which is fairly ‘locally optimal’, so in good hands they can absolutely be used to build correct software.

      Humans produce code which is fairly ‘locally optimal’

      Also, interesting you use ‘ as a quote rather than '. I notice these quotes are used with LLM generated text, as I can't find this on my keyboard.

      1 reply →

If it can transform into Winamp I don't care if the code is LLM generated, typed by infinite monkeys or found in some ancient scrolls.

Jokes aside, how can you be sure that the official Spotify app (or any app, or Windows) was not written by a LLM without supervision?

  • Not OP but I don’t really care if it was or not. All I know is that I’ve been using the Spotify app 10+ years and it works well. I don’t know if this random app works, and if it hasn’t been supervised I doubt it does.

    • Gave it a quick try today, it works pretty well and is noticeably faster than the official app.

  • The official Spotify app has some skin in the game. Random dudes self promotion project, not so much.

    • I suspect the official app would actually be more consistent and not as bad to use if it was generated by an LLM.

I too enjoy wearing the RealPlayer skin of the 90's. Makes me look very chic.

  • If the last twenty years of horror movies have taught me anything it is that maybe you can't be a real player, but you can always wear their skin!

LLMs seem to have been fine-tuned to use metaphors, presumably because they read like vivid creative writing. The over-use of metaphor in LLM-produced text is exhausting.

Slop code is already hard to tolerate, but any hint of slop in text will immediately make me chuck it into the bin / close the tab, no exceptions. My lifetime is finite, I'm sure as fuck not gonna spend time reading something that a person could not even be arsed to write themselves. I'm only annoyed that it takes sometimes a few seconds, sometimes a few minutes, to detect that I'm actually not reading a person's thoughts but only a machine simulacrum of such.

I highly recommend anybody to take up a similar rule, in any context. Slop in a website? Close. Slop in an email? Bin. Slop in a code comment? Skip.

Uncanny valley. LLMs are great at producing text that reads almost right.

Your comment has too much intensity as well. Honestly it too looks like slop. I agree with what you said, but nevertheless your writing is likely AI generated here, it’s very obvious.