• 115 Posts
  • 150 Comments
Joined 2 years ago
cake
Cake day: August 28th, 2024

help-circle









  • No, it is not the same thing. A downvote is disapproval, an upvote is approval, and no vote is neutral.

    I find it interesting that you see my “downvote = negativity” as an interpretation problem, but that you don’t see that what you just wrote is your interpretation of the buttons. At no place in any Lemmy documentation and not anywhere in any Lemmy app or web app is written what you just wrote. It’s your interpration of the meaning of the buttons.

    For me:

    • Upvote can be approval or even a something I disagree with, but is well argued or I want to see more of it
    • Clicking nothing means “I don’t care”
    • Downvotes are disabled by my instance, which is good. I can’t see downvotes and can’t give them.
    • Comments allow me to disagree and share my arguments why I disaggree (as I do now).
    • And if something is so bad that it should be gone, there is still the possibility to report a post or comment

    The only way to have the same outcome than a downvote with only upvotes is to upvote every single other comment

    But why is that even necessary? Why are you even wasting your energy to click that button? If it’s really bad, one can report it. If it’s not worth to report, one can leave it and focus on other stuff. I seriously don’t understand it. My only explanation is “doing it like that because we have always done it that way” and this is why I totally understand why most big platforms removed such a downvote feature.

    If you are downvoted more than upvoted, then you know your opinion is unpopular. Doesn’t meant it’s bad or good.

    Not even unpopular in general… Unpopular in a specific bubble at a specific time. But I agree. Combined with a karma system, it’d unfortunately by a toxic combination… (Reddit)

    For instance, I neither downvoted nor upvoted your comment, because I consider it a valuable part of the conversation, but I still don’t approve it.

    That confuses me now, because it feels like the point I’m trying to make.

























  • You can spend a minute reading the manual instead. Next time you do it, you can do it faster than through the LLM.

    I talked about writing a script that can be 20 to 50 lines. That costs me far more than “a minute” of manual reading. I generate the script, I review it, I execute it and then throw it away. Sounds like a win-situation for me. I have more time for my actual homework.

    Autocompleting a block of code

    I wrote “Code-line” completion by the way, not “Code block” completion.

    Autocompleting a block of code is a sign that you are not writing anything new and a signal to think about whether there is semantic duplication in the code that should be explored.

    Have you ever tried it out (e.g. GitHub Copilot)? Not sure what you mean exactly, especially by “writing anything new”. It can of course auto-complete stuff that does not exist in the code base. There is lots of code in the training data. Or do you mean “writing completely new stuff that hasn’t been written by anyone”? Because only few people do that, I guess.


    One more good usage I experienced is giving it text (e.g. a documentation file for customers) and the task to find/fix the typos. I’m pretty good at finding them (at least in my native language German), but you probably guessed it: I’d rather do other stuff.


  • I think, there are useful use cases and bad ones.

    bad

    • “Generate me a web project for XY” is fine to see what a prototype could look like, but pushing that to production is a bad idea IMO.
    • “Write me unit tests for XY” is bad IMO. At this point, the unit tests are bureaucracy.
    • “Generate documentation”… same… At this point, documentation is bureaucracy, but I have seen that in the years before AI, too.
    • “Writing commits and pull requests or tickets”… I don’t like that use case either. I’m able to find my commits or bugs later, because I remember words. I like writing them myself.

    don’t know

    • have never used it to review my commits…

    good

    • Generate me a throw-away shell script to do XY (I can still modify it if I want to), but Bash/PowerShell/… are not my main programming languages and it saves me time. Of course, doing it this way, I won’t learn them. I’m aware of that.
    • Aiming it on code to find bugs is the most useful use case I found so far.
    • Code-line completion is also often useful. It completes what I’m thinking.

    If you think LLM is good at X, it’s because you really really suck at X

    I though similar a year ago, but nowadays, I disagree. Around Claude 4.6, that changed.

    • I think, giving it a piece of the code base and letting it find a bug does not prove that I don’t have the skill to do so. I just don’t have the time to go through the whole code base. But I have the time to analyze a potential bug and see whether it’s a real one.
    • This guy disagrees with you, too… A year earlier, he said, AI was not usable, because they are doing too complex stuff. https://devblogs.microsoft.com/dotnet/ten-months-with-cca-in-dotnet-runtime/

    Moral: The technology won’t go away. I am honest: I preferred the times before LLMs, too… And I hate how some people with a coding agent turn off their brain and commit bullshit. I have seen it. But saying that it does not (or even will not) bring any benefit and that the users all suck at their job is far from true.