The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Email Subscription

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 717 other subscribers

Archive for the ‘Quality Assurance’ Category

pixelfed: “Pixelfed bans AI generated contributions…” – Mastodon

Posted by jpluimers on 2026/09/30

Recently someone commited a large set of LLM (Large Language Model often wrongly called AI or Artificial Intelligence as at best they are an AI model, or better phrased machine learning model, not even a machine learning reality¹) assistance files to the pixelfed repository. This caused quite some turmoil resulting in pixelfed banning AI generated contributions.

This is for good reason: too many LLM generated commits lack quality control. This results in shoving the burden of the checks from the contributor to the volunteers of the project teams. Those volunteers are already overwhelmed anyway (there is always an applicable XKCD, in this case [Wayback/Archive] 2347: Dependency – explain xkcd).

The offending commit was [Wayback/Archive] Add AI docs · pixelfed/pixelfed@65dff00 · GitHub. The contributor was lazy enough to wrongly name this commit, as these weren’t docs in the sense of documentation, but a set of Claude Skills and other LLM slop².

That behaviour is exemplary for almost all LLM contributions: most humans and systems generating them take them for correct and just commit their content.

I am still not convinced that the main contributor switching within a few days from “oh, let’s add LLM stuff” into “nope, we are not going to allow LLM” vows for a strong soul.

The Pixelfed statement is via [Wayback/Archive] pixelfed: “Pixelfed bans AI generated contributions…” – Mastodon

Read the rest of this entry »

Posted in Agile, AI and ML; Artificial Intelligence & Machine Learning, Claude, Code Quality, Development, Generative AI, JavaScript/ECMAScript, LLM, PHP, Quality Assurance, Scripting, Software Development, Vue.js | Leave a Comment »

Tom Schuster: “To my security peeps: Was the introduction of widespread fuzzing similar to AI-based bug hunting now, or is this really a different beast?” – Hachyderm.io

Posted by jpluimers on 2026/09/29

Interesting question with (too few but) nice comments: [Wayback/Archive] Tom Schuster: “To my security peeps: Was the …” – Hachyderm.io

  1. To my security peeps: Was the introduction of widespread fuzzing similar to AI-based bug hunting now, or is this really a different beast?
  2. @evilpie IMHO it’s very similar, definitely larger scale though
  3. @buherator @evilpie agree that it is similar, it feels like the larger scale is mainly because the security industry grew and many people experiment with LLMs. Prompting seems more intuitive than writing a harness for AFL, so it’s probably more how humans approach than the tool. It’s just another tool.
  4. Signal to noise ratio is worse with LLMs but but but but but
  5. @floyd @evilpie I tried to avoid elaborating on “scale” because it refers to many things in this case, e.g.:- How easily you can adapt to a new target (vs. AFL)
    – How much power is available for the task (GPU acceleration)
    – Number of bug classes you can (trivially) aim for (vs. fuzzing for logic bugs)
    – etc.

--jeroen

Posted in Agile, Code Quality, Development, Quality Assurance, Software Development | Leave a Comment »

QA frustrations: waiting  almost a year for a resolution

Posted by jpluimers on 2017/11/29

A frustrating part of reporting issues to many companies is the time it takes to get a response at all or a response “maybe in the far future”.

Below is just an example, but I see this regularly, for instance another example (scheduled in a later security related post) a company that responds to a “welcome in the 21st century” complaint on enforcing a 16 character password limit by responding “maybe we are going to extend it in the 22nd century”.

[WayBack] why are the parameters in a reverse order.

–jeroen

Posted in Development, Quality Assurance, Software Development | Leave a Comment »