Any idea what happened that allegedly caused slopped vulnerability reports to improve? mastodon.social/@bagder/116364045995306922 claims they got much better while not that long ago they were shutting down the bug bounty, because they were drowning in slop. Is it because people actually polish those or it’s just a matter of defining a goal function and just burning the rainforest until the slop extruder hits the jackpot? Or is this another case of the LLMentalist?

If you found this post helpful, follow me for more content like this.

So they expect more cases of data being lost like this?

When I do code review these days, sometimes I genuinely can’t tell whether I’m talking to the person or to the slop extruder. It often ends up with me repeating the same comment over and over again.

The “we’ll save some bucks by removing physical knobs and pose this as futuristic by making some vital functions only accessible via multiple levels of menus on a touchscreen” thing is the worst and should be banned.

Technically superman is a more correct translation for that word (similarly to how superscript is the thing beyond the script)

All roads lead down from the local maximum

It’s a treasure trove of hilariously bad takes.

There’s nothing intrinsically valuable about art requiring a lot of work to be produced. It’s better that we can do it with a prompt now in 5 seconds

Now I need some eye bleach

Rich Hickey joins the list of people annoyed by the recent Xmas AI mass spam campaign: gist.github.com/…/ea94e3741ff0a4e3af55b9fe6287887…

Cory’s talk on 39C3 was fucking glorious: …ccc.de/…/39c3-a-post-american-enshittification-r…

No notes

Digressing: The irony is that it’s a language with one of the best standard libraries out there. Wanna run a http reverse proxy with TLS cross compiled for a different os? No problem!

Many times I used it only because of that despite it being a worse language.