• 9 Posts
  • 738 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle


  • Ephera@lemmy.mltoScience Memes@mander.xyzOopsies
    link
    fedilink
    English
    arrow-up
    17
    ·
    2 days ago

    Yeah, the formulation is a bit off here. With opt-out, you have no way to measure consent, because you can’t discern between people who actually consent and those who just haven’t opted out, for lack of knowledge or other reasons.

    These societies have simply weighed up the two options and decided that saving lives is more important than leaving personal freedom intact at all costs.


  • What I don’t like about the genre, is that I’m bad at it. 🙃

    More seriously, I do find it kind of frustrating at times. Restarting ten times in a roguelike, no problem, because it’s always a new challenge.
    But if I miss the same jump ten times, or have to retry the same platforming passage ten times, you’ll see me getting impatient, which means I’ll fail the next ten attempts, too…




  • Ephera@lemmy.mltoProgrammer Humor@lemmy.mlDesigners cry quietly
    link
    fedilink
    arrow-up
    45
    arrow-down
    3
    ·
    3 days ago

    I, unfortunately, have to use GitHub at $DAYJOB and this is me. I navigate most of the webpage via the URL bar now.

    Basically, let’s say I’m working on a repo github.com/tomato/sauce/ and want to navigate to the Releases page.

    Via the webpage:

    1. Type github.com into the URL bar.
    2. Don’t find tomato/sauce/ in the list of recent repos, even though it’s the only repo I work on.
    3. Click on some other repo that’s at least in the tomato/ org.
    4. Navigate up to the tomato/ org.
    5. Find the sauce/ repo in the list.
    6. Traverse half the fucking screen to hit the “Releases” heading in the middle of the About-section.

    Via the Firefox URL bar:

    1. Type gi→t→s→r→.
    2. Hit Enter.

    I admit, it’s hard to compete with the latter, but I wouldn’t know how to navigate that way, if the former wasn’t so terrible.












  • Well, for reasons, I happen to know that this person is a student, who has effectively no experience dealing with real-world codebases.

    It’s possible that the LLM produced good results for the small codebases and well-known exercises that they had to deal with so far.

    I’m also guessing, they’re learning what a PR is for the first time just now. And then being taught by Microsoft that you can just fire off PRs without a care in the world, like, yeah, how should they know any better?


  • Tangentially related rant: We had a new contributor open up a pull request today and I gave their changes an initial look to make sure no malicious code is included.
    I couldn’t see anything wrong with it. The PR was certainly a bit short, but the task they tackled was pretty much a matter of either it works or it doesn’t. And I figured, if they open a PR, they’ll have a working solution.

    …well, I tell the CI/CD runner to get going and it immediately runs into a compile error. Not an exotic compile error, the person who submitted the PR had never even tried to compile it.

    Then it dawned on me. They had included a link to a GitHub Copilot workspace, supposedly just for context.
    In reality, they had asked the dumbass LLM to do the change described in the ticket and figured, it would produce a working PR right off the bat. No need to even check it, just let the maintainer do the validation.

    In an attempt to give them constructive feedback, I tried to figure out, if this GitHub Copilot workspace thingamabob had a Compile-button that they just forgot to click, so I actually watched Microsoft’s ad video for it.
    And sure enough, I saw right then and there, who really was at fault for this abomination of a PR.

    The ad showed exactly that. Just chat a bit with the LLM and then directly create a PR. Which, yes, there is a theoretical chance of this possibly making sense, like when rewording the documentation. But for any actual code changes? Fuck no.

    So, most sincerely: Fuck you, Microsoft.