Comment by ramon156

18 days ago

Pro tip (sorry if these comments are overdone), write your posts and docs yourself (or at least edit them).

Your docs and this post is all written by an LLM, which doesn't reflect much effort.

People have already fried that part of their brain, the idea of writing more than a couple sentences is out of the question to many now.

These plagiarism laundering machines are giving people a brain disease that we haven't even named yet.

  • Oh cmon, at least try to signal like you're interested in a good-faith debate by posting with your main account. Intentionally ignoring the rules of HN only ensures nobody will get closer to your belief system.

    • I mean his rage is somewhat warranted, there is a comment a few threads up of a guy asking what model comparable to Opus 4.6 can be run on 16 gb VRAM...

      Supporters and haters alike, its getting pretty stupid out there.

      For the millionth time, it seems learning basics and fundamentals of software engineering is more important than anything else.

> which doesn't reflect much effort.

I wish this was an effective deterrent against posting low effort slop, but it isn't. Vibe coders are actively proud of the fact that they don't put any effort into the things they claim to have created.

  • Github repo that is nothing but forks of others projects and some 4chan utilities.

    Professional codependent leveraging anonymity to target others. The internet is a mediocrity factory.

  • [flagged]

    • EE with decades of experience here. You have valid points (SWE tedium, LLMs allowing adjacent technical fields to access SW/FW work without involving SWEs) that are completely lost because you're being an asshole for no good reason.

      1 reply →

counterargument: I always hated writing docs and therefore most of thing that I done at my day job didn't had any and it made using it more difficult for others.

I was also burnt many times where some software docs said one thing and after many hours of debugging I found out that code does something different.

LLMs are so good at creating decent descriptions and keeping them up to date that I believe docs are the number one thing to use them for. yes, you can tell human didn't write them, so what? if they are correct I see no issue at all.

  • > if they are correct I see no issue at all.

    Indeed. Are you verifying that they are correct, or are you glancing at the output and seeing something that seems plausible enough and then not really scrutinizing? Because the latter is how LLMs often propagate errors: through humans choosing to trust the fancy predictive text engine, abdicating their own responsibility in the process.

    As a consumer of an API, I would much rather have static types and nothing else than incorrect LLM-generated prosaic documentation.

    • Can you provide examples in the wild of LLMs creating bad descriptions of code? Has it ever happened to you?

      Somehow I doubt at this point in time they can even fail at something so simple.

      Like at some point, for some stuff we have to trust LLMs to be correct 99% of the time. I believe summaries, translate, code docs are in that category

      5 replies →

  • > if they are correct I see no issue at all.

    I guess the term "correct" is different for me. I shouldn't be able to nitpick comments out like that. Putting LLM's aside, they basically did not proof-read your own docs. Things like "No python required" are an obvious sign that you 1. Started talking about a project (you {found || built} in python), want to do it in Rust (because it's fast!) and then the LLM put that detail in the docs.

    If they did not skim it out, then they did not read their own documentation. There was no love put into it.

    Nonetheless, I totally get your point, and the docs are at least descriptive.

    > LLMs are so good at creating decent descriptions and keeping them up to date

    I totally agree! And now that CC auto-updates memories, it's much easier to keep track of changes. I'm also confident that you're the type of person to at least proof-read what it wrote, so I do not doubt your validity in your argument. It just sounds a lot different when you look at this project.

  • engineer who was too lazy to write docs before now generates ai slop and continues not to write docs, news at 11