← Back to context

Comment by jchw

2 hours ago

Nah, it's not just that, literally all the stuff they've posted this year is obvious LLM writing, none of the stuff from previous years is. To get this close to LLM writing style without actually using an LLM, you would pretty much have to be purposefully trying.

But I have a new favorite way of demonstrating this:

https://github.com/search?q=owner%3Axoreaxeaxeax+load-bearin...

Guess how many of these are from before 2025.

Like, who cares? In today's present, I wouldn't bother writing the article myself neither besides giving the instructions and auditing the output. Substance is what matters

  • > I wouldn't bother writing the article myself neither besides giving the instructions and auditing the output.

    The article would be better with just the instructions and audited output. All the LLM added bloat is tiring and distracting; it's like an article from New-Yorker or Wired.

  • I struggled to understand the article, it doesn't properly explain what the exploit is in a way I could immediately understand, after staring at it for a bit and reading comments here I think it's a hardware register that's exposed to user software that shouldn't be but I really didn't understand that at first glance ("Poke the DRAM controller" made me think a hardware exploit) and I'm still not sure if I'm right about that (if it is, just start by explaining that instead of all the unnecessary filler and diagrams and animations of the Mona Lisa being scrambled and talk of bath salts which I still don't understand the relevance of)

  • > Like, who cares?

    You are literally asking this to people who clearly care...

    > In today's present, I wouldn't bother writing the article myself neither besides giving the instructions and auditing the output.

    Then why exactly are you even bothering to reply to me instead of having Claude do it and auditing the output? If HN didn't have a rule against it, would you even bother replying yourself?

    But really, there's a fair bit more to unpack here than just that. Why wouldn't you bother? Is writing a README.md about some project you worked on really that hard? Even with heavy LLM assistance, I'd wager to guess this project, which clearly involved working on real hardware, was more than just prompting. So clearly there was human effort other than prompting. And I do respect that, but I want people who write things to respect my time. I'm not asking them to disclose every tool they use, I'm asking them to not waste our time with crappy irritating Claude writeups. Whether it's explictly specified or not, we know.

    Frankly I struggle to believe that people don't really mind if someone else speaks for them in their own voice, just because they're too fucking lazy to speak for themselves anymore. We've had competent GenAI for like a year or two, at this rate people are going to forget their potty training in another few months.

    > Substance is what matters

    Substance matters, which is not great for LLMs, because they put out text that has far more fluff than substance. What, however, is far worse for LLMs, is the fact that kick and scream and cry all you want, but: style and presentation matters, too.

    It is absolutely true that if you just dropped a very brief blurb that all AMD CPUs from a certain generation can be pwned it would have a decent chance to hit the HN frontpage just out of sheer interestingness. That is not because the style and presentation doesn't matter, it's just that the substance is significant in spite of the bad presentation and style.

    And absolutely, we can easily forgive someone for simply not being very good at the presentation and style part, certainly I'm not really an expert at it. But this author has released plenty of great hits before, so I damn well know they can. It's a serious disappointment to see them downgrade to irritating, grating Claude garbage output.