Want to wade into the sandy surf of the abyss? Have a sneer percolating in your system but not enough time/energy to make a whole post about it? Go forth and be mid: Welcome to the Stubsack, your first port of call for learning fresh Awful you’ll near-instantly regret.

Any awful.systems sub may be subsneered in this subthread, techtakes or no.

If your sneer seems higher quality than you thought, feel free to cut’n’paste it into its own post — there’s no quota for posting and the bar really isn’t that high.

The post Xitter web has spawned soo many “esoteric” right wing freaks, but there’s no appropriate sneer-space for them. I’m talking redscare-ish, reality challenged “culture critics” who write about everything but understand nothing. I’m talking about reply-guys who make the same 6 tweets about the same 3 subjects. They’re inescapable at this point, yet I don’t see them mocked (as much as they should be)

Like, there was one dude a while back who insisted that women couldn’t be surgeons because they didn’t believe in the moon or in stars? I think each and every one of these guys is uniquely fucked up and if I can’t escape them, I would love to sneer at them.

(Credit and/or blame to David Gerard for starting this.)

    • Seminar2250
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      2 months ago

      this comment:

      Unless you’ve only ever used ChatGPT, you will know that LLM-produced code is not the result of a single prompt, not even a conversation, but rather a workflow that often goes as such:

      • Discuss a problem with the LLM. The LLM autonomously reads large parts of the repository you’re working in, during the discussion.
      • Ask it to write a plan. Edit the plan. Ask it about the edited plan. Edit it some more.
      • Repeatedly restart the LLM, asking it to code different parts of the plan. Debug the results. Write some code yourself. Create, rebase, or otherwise play around with the repository; keep multiple branches of potential code.
      • Go back and edit the original plan, now that you know what might work. Port some unit tests back in time, sometimes.
      • Repeat until done.

      is so stupid

      • froztbyte
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 months ago

        rubber duck debugging with a cost multiplier magnitude coming in at a couple of zeroes tail end of the figure

        and worse results