‹ BackHN Continuity

Thread

Amiga Unix, Again

144 points · 67 comments · doener

  1. jchw · · focus · HN ↗
    My eternal advice to anyone doing heavily LLM assisted projects is to do them a bit less LLM assisted. You should still use LLMs, in my opinion, they're wonderful tools. But I know reading this page that this text is mostly LLM-generated, and that leaves there to be little hope that much else of the project isn't.

    It's one thing if your code is really truly "co-authored by" Claude. It's another thing if it isn't even really co-authored by you.

    Evidently the majority of people see no problem with LLM prose, but me and many others think it is some of the most annoying crap possible. Please consider speaking in your own voice.

    I know this gets repetitive, but it is important.

    1. jonathanstrange · · focus · HN ↗
      It's not important at all and I wish people would stop mentioning AI. If you have criticisms on the docs or code, by all means make them but they shouldn't concern "AI vs human" considerations. Humans have written plenty of bad and documentations, too, it really doesn't matter who wrote what to what extent, what matters is whether it's the right quality.
      1. steve1977 · · focus · HN ↗
        Since we cannot address criticism on the docs or code to the author, we have to address our criticism to the middleman and what he did.
        1. jonathanstrange · · focus · HN ↗
          That attitude unfortunately leads to people criticizing something without having enough evidence about it in the first place, like criticizing a book and later admitting you've only seen the cover and read the summary on the back.

          Criticisms should have substance.

          1. steve1977 · · focus · HN ↗
            I can criticize the cover of a book though, without having read the book.
            1. jonathanstrange · · focus · HN ↗
              I guess you can do anything you like if you don't care when people don't take you seriously.
        2. kdjdkcneixj · · focus · HN ↗
          People really need to learn that using AI to build something doesn’t automatically mean you just left every plan, spec and decision up to the AI.

          Can you do that? You absolutely can. Does everyone do that? No, absolutely not.

          It’s not a black and white issue. And, honestly, it’s quite narrow sighted and narrow minded to think so.

          The dev is not the middleman because Claude is not the author. Claude is the tool.

          1. steve1977 · · focus · HN ↗
            This is unfortunately not the reality I'm seeing at my workplace. If this is still different for you, be happy and enjoy it while it lasts.
      2. Sharlin · · focus · HN ↗
        No. It’s dishonest, not in any way different from plagiarizing another human’s text or code without proper attribution.
        1. jonathanstrange · · focus · HN ↗
          I've written a lot in my life so far, including books and novels, and never used AI for it. I don't see the parallel. If you were right and it was the same as plagiarizing, then the use of AI should be prohibited entirely. However, to me it appears more akin to using tools like spell checkers, CAS pocket calculators, and Grammarly. It's another tool. I don't really get the fuzz people make about AI. I'm also fond of judging the content of texts regardless of the author. Has that idea come so much out of fashion?
          1. Sharlin · · focus · HN ↗
            Because plagiarization is not illegal. It’s just unethical and dishonest, and in certain contexts where your work is directly related to your status or compensation, it gets you in trouble. Copyright violation is a specific type of plagiarism that is illegal, but LLM output is not and, in current legal understanding, can not be copyrighted.

            Using the services of a human editor is not plagiarism, and mere editing is not considered coauthorship. Mentioning or thanking the editor is just a courtesy, or a contractual obligation at most. LLMs don’t need thanks so most people probably agree it’s fine not to mention it in a casual blog post if its part really is just editorial, brainstorming aid, or similar. (But context-specific terms and conditions apply, obviously.)

            What is absolutely not editorial use is making a hundred-word prompt and asking an LLM to expand it to a thousand-word blog post, or a thousand-line computer program, just like it wouldn’t be to ask or pay another human to do it for you. At most you’re then a coauthor of the LLM. This should be obvious, really, we have literally hundreds of years of history on the ethics and norms of assigning authorship on creative works. LLMs should change very little of that.

            And then there’s the quality issue. If there were a human author that ghost-wrote blog posts or program code for people, and their output would always have the same known quality and accuracy issues, I’d want to be warned rather than having to spend time on figuring it out every time. Reputation matters.

            1. jonathanstrange · · focus · HN ↗
              Your arguments aren't convincing. LLMs do not have authorship, they aren't persons. These ramblings about plagiarism are irrelevant, they're a classic case of "topic missed."

              The same for human editors, about whom I have slightly more nuanced view. I do believe that some of them are offering services that amount to ghostwriting and are often unethical. I've seen people make careers in the humanities where I'd say the paid editor (who also had studied the subject area) would at least be a co-author, if not the person who in the end deserved most of the credit. I've seen that with my own eyes as someone who worked for 20 years as a researcher in academia. That's why I've always rejected private editors that many of my colleagues have employed. It's a deeply unethical practice, not at all as harmless as you describe it.

              That being said, the comparison to editors also doesn't apply because, again, LLMs aren't persons and do not have authorship. They neither are persons and authors in a legal sense, nor does it makes much sense from an ethical perspective to grant them personhood and authorship. If that made sense, then I'd agree with you that they should be mentioned as co-authors or authors. I'd have no problem whatsoever with academic and other works written by LLMs and giving credit to them. However, I don't see we're there yet.

              Regarding the quality issue: What I'm saying and what my stance is is exactly that the works of persons or LLMs or persons who use LLMs for writing code or texts must and should always be evaluated the same, namely based on the merits of the content alone. That would be even more important if LLMs were persons and could be attributed authorship -- but they can't.

              You arguments don't work because they're based on incorrect assumptions about what LLMs are. They are tools. You might find it dishonest when people use them without stating that, and that's fine, but then you shouldn't base your views on unrelated issues like plagiarism, copyright, and editors. My hunch is that people like you simply can't cope with the change, and, again, I'm saying that as someone who barely uses AI for programming and has never and will never use it for writing. Please stop the whining. I'll be honest, to me personally, these anti-AI rants are intellectually insulting because they seem to imply that humans cannot stand against AI by the quality of their own works and require some extra protectionism.

      3. layer8 · · focus · HN ↗
        Obviously LLM-generated text generally doesn’t have the right quality. People aren’t just annoyed by it being LLM-generated, they are annoyed because the writing is bad in a soulless way.
      4. jibal · · focus · HN ↗
        The GP writes "me and many others think ...". I find that many of the complaints about the way LLMs write come from people who are illiterate and haven't been exposed to much literate writing before.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.