• 0 Posts
  • 28 Comments
Joined 3 years ago
cake
Cake day: July 24th, 2023

help-circle



  • True, that might happen at some time in the future, I’ll believe it when I see it. But at the moment most of the generated images or texts are only good enough if a human sloperator does some quality control and regenerates or edits the results until they look good. All the models i’ve seen so far have specific quirks/preferences which repeat as patterns. This might not be immediately apparent when a new model comes out, but it takes a lot less time to identify the quirks than it takes to train the model in the first place.

    To be clear, I’m not implying that I couldn’t be fooled by a genAI text or image, but the majority of uncontrolled zero-shot slop is easy to spot, because it is just that, slop. Look at any random slop readme.md in a github repo for example. The structure is always the same, it is filled with a collection of words that tries to mimick what a readme would look like, including weird jargon imitations but it lacks the clarity, personal touch, developer ego and soul it would have if a real author was writing about his own cherished creation. Look for the things that are absent instead of the things that are there. Same for identifying slop images… Image Gen focuses on the subject and gets sloppy on the “less important” bits, like backgrounds.




  • I don’t entirely agree with the doom and gloom of that article. Humans are particularly good at adapting to changes. And humans are particularly good at detecting patterns and anti-patterns. Patterns are signals, and while adaption will take a while and will be painful, I think we’ll work it out. For example, detecting AI slop reliably and intuitively is a skill that more and more people learn. Once the pattern is learnt, it’s a new useful signal. Other new signals emerge for quality detection. In a world of crap software, the few that work well will stand out. Anything that can be “created” by anyone with a few prompts loses its value. What’s valuable will be what stands out from the slop.



  • Ok, I’ll bite. Assuming that the article means Large Language Models exclusively when mentioning “AI”.

    Good specialized models aren’t that easy to build for a lot of use cases.
    Coding is one of the more problematic cases. People tend to think that coding is about code, so if we just create a model that is specialized in writing code, we’re golden. However it turns out this isn’t true. Coding is not only about code itself, but about creating an application that has a specific purpose and features in a specific domain. The LLM needs an understanding of not only the plain code, but needs knowledge about the subjects the application is about, and these are mostly in the domain of general knowledge. Another issue is that the model itself needs to communicate with the user in an appropriate way, and this needs general knowledge as well.

    “Summarize documents, draft memos, analyze spreadsheets”

    All these examples require an LLM to have a good general knowledge to grasp what the original text is about. You won’t get a decent summary when the general knowledge of the subject at hand is subpar. My point is, bigger LLMs with more general knowledge handle these tasks better than smaller ones. I’m not saying smaller models can’t do the job, but there will be differences in quality.

    It’s not that hard to let existing LLMs use specialized knowledge.
    The actual problem is to prevent this specialized knowledge from being stolen by US/Chinese AI companies. So instead of focusing on building own “specialised” models, let’s work on preventing the ongoing theft of knowledge, and using the right tools for the job.



  • What do you think where this is going to end up? My personal assessment of the situation is that only the mega-corporations can afford enshittification like that, and even those are now getting a taste of their own medicine (Sloperators recreating their flagship products… it’s a race to the bottom with enshittification on one side and sloppy replacements on the other). Smaller sized companies will simply get buried when the quality of their products falls to garbage levels. This is what those smaller sized companies don’t realise yet: When everyone can churn out the same low quality slop, their USP and their customers are gone soon.


  • Let them, but insist they should also use Claude to QA their code and thus take responsibility for the whole thing. If they trust AI to be good enough, why not go full circle? That shouldn’t be a problem, right?

    Joking aside, I know there is a real danger of those people shifting the responsibility for their created code mess downwards to the developers and QA, and when shit inevitably hits the fan they know who to blame.


  • Ghost pairing ist ein irreführender Begriff. “Digital incompetence” trifft es eher. Das potenzielle Opfer muss gleich mehrere dumme Dinge tun:

    • die eigene Telefonnummer in eine nicht vertrauenswürdige Website eingeben
    • einem Warnhinweis ignorieren und einfach auf “Ok” drücken ohne zu lesen oder zu verstehen was dort angezeigt wird

    Aber tatsächlich wäre es vermutlich sicherer wenn der Nutzer im Messenger initial selbst seine Paarungswilligkeit anzeigen müsste bevor eine solche Paarungsanfrage überhaupt möglich wird. So wie bei Bluetooth, wo die Auffindbarkeit explizit eingeschaltet werden muss und nur ein paar Minuten aktiv bleibt.