Gigi

Not doing DMs. Aspiring Saunameister.

there’s a fine line between just doing things and just doing damage to things

Source: dergigi.com

Slopmonger

Source: www.etymonline.com

This avalanche is going to make maintainer overload even worse.

Source: daniel.haxx.se

You can tell by the way they are worded

Source: daniel.haxx.se

I complained and I complained about the high frequency junk submissions to the curl bug-bounty that grew really intense during 2025 and early 2026. To the degree that we shut it down completely

Source: daniel.haxx.se

The AI tools will improve further and the researchers can find new and different ways to prompt the existing AIs to make them find more. We have not reached the end of this yet.

Source: daniel.haxx.se

AI powered code analyzers are significantly better at finding security flaws and mistakes in source code than any traditional code analyzers did in the past

Source: daniel.haxx.se

My personal conclusion can however not end up with anything else than that the big hype around this model so far was primarily marketing

Source: daniel.haxx.se

curl is one of the most fuzzed and audited C codebases in existence

Source: daniel.haxx.se

The source code consists of 660,000 words, which is 12% more words than the entire English edition of the novel War and Peace.

Source: daniel.haxx.se

Completely unscientific poll on Mastodon about people’s expectations for Mythos scanning curl

Source: daniel.haxx.se

lose touch

Source: larsfaye.com

you cannot understand code without engaging with it

Source: larsfaye.com

the countless failed attempts at trying to democratize coding while not understanding coding

Source: larsfaye.com

lean on them to brainstorm

Source: larsfaye.com

The financial, and intellectual, rug-pull could come at any moment

Source: larsfaye.com

It's not unreasonable to play this pattern forward, where we could be creating an industry where you need to pay for token consumption to accomplish something that used to be the product of your own critical thinking and problem-solving abilities.

Source: larsfaye.com

Every new model release follows the same pattern of high benchmarks, followed by hype, followed by the reality of usage and everyone complaining of them being "nerfed" and burning through 2x-3x as many tokens to get the same job done.

Source: larsfaye.com

the models themselves are built on shifting sands

Source: larsfaye.com

What used to be a skill that they could execute with just a keyboard and text editor suddenly required a subscription to an AI model provider.

Source: larsfaye.com

You cannot replace a deterministic system with a probabilistic one and expect zero ambiguity.

Source: larsfaye.com

What you say is often not what you mean, and LLMs fill in ambiguity with assumptions (or hallucinations), which leads to: more review, more agent revisions, more tokens burned, and more disconnection from what is being created.

Source: larsfaye.com

"To grow skills, people need to go through hardship. They need to develop the muscle to think through problems," he said. "How would someone question if AI is accurate if they don't have critical thinking?"

Source: larsfaye.com

effectively using Claude requires supervision, and supervising Claude requires the very coding skills that may atrophy from AI overuse

Source: larsfaye.com

It actually is different this time.

Source: larsfaye.com

a higher level of ambiguity is not a higher level of abstraction

Source: larsfaye.com

in an ironic twist of fate, it's the individual's critical thinking skills and cognitive clarity that AI tooling has now been proven to impact negatively

Source: larsfaye.com

only a skilled developer who's thinking critically, and comfortable operating at the architectural level, can spot issues in the thousands of lines of generated code, before they become a problem.

Source: larsfaye.com

pulls the slot machine lever over and over, iterating and reiterating with often multiple agent instances until it's done

Source: larsfaye.com

provide "good taste"

Source: larsfaye.com

respect the community, and only share what is truly relevant

Source: rmoff.net

the community would be better off without your contribution

Source: rmoff.net

If you dump a complex PR into a project without due care, you’re obligating the reviewers to go through the code and for them to explain to you why it can’t be merged.

Source: rmoff.net

Asymmetry of Bullshit

Source: rmoff.net

another way of showing respect to the community is to be very open and clear about if, how, and where you’re using AI in your contribution.

Source: rmoff.net

Read the room, and get a feel for whether they’ll welcome with open arms your AI slop—or not.

Source: rmoff.net

the netiquette is always to "lurk"

Source: rmoff.net

Respect

Source: rmoff.net

Throwaway tools are just fine.

Source: rmoff.net

Does your offering contribute anything

Source: rmoff.net

thoughtful and careful design

Source: rmoff.net

AI is a powerful tool, and I will argue with anyone for the case that it’s pretty much a dereliction of one’s job to not be including it in one’s toolbox.

Source: rmoff.net

Built with AI, not by AI

Source: rmoff.net

with AI-generated content, whether a vibe-coded app or a blog post, the same applies.

Source: rmoff.net

Who cares.

Source: rmoff.net

Sharing content online is wonderful. It’s pretty much what made the internet what it is today.

Source: rmoff.net

common decency and taste

Source: rmoff.net

with the care and good intent of a human

Source: rmoff.net

There’s good 'slop' and bad slop

Source: rmoff.net

AI slop is driving up the noise, and making the signal more and more difficult to discern

Source: rmoff.net