#slopware

5 posts · Last used 6d

i found the perfect analogy vor "AI" use Using AI is like eating fast food. Technically it is food, you get "full", but not in a sustained way. Instant but shallow gratification. Once in a while its fine, but only eating fast food will have consequences. It feels cheaper, but gets expensive really fast if eating a lot of it. You don’t need skill or effort to get it. Its addictive. It is healthier to never eat fast food. #ai #genai #chatgpt #slop #vibecoding #llm #slopware #aislop #claude
3
0
2
1
uuuugggghhh, this is a bit late, but I haven't seen any posts about it... apparently Incus and IncusOS, both of which had a zero-tolerance policy toward LLM use, "now tolerate the use of [LLM] tools" The change to their contributor guidelines was committed on June 16, which was included in release notes for Incus 7.2 and Incus 7.0.1 LTS. https://linuxcontainers.org/incus/docs/main/contributing/introduction/#for-contributions https://github.com/lxc/incus/commit/54bae0e4d4eabfe0f1a1127b5fb0dfc986720654 Most of the new policy elaborates on the idea that code should be "submitted by human beings" (submitted) who "fully own their contribution" (lol) and are "able to reason about it [and] explain why things were done a particular way". You know, "responsible" vibecoding, a thing that totally exists... assuming you can ignore the myriad ecological/social/legal/technical/etc issues related to the production and use of LLMs, you're cool with using fashtech, and you want to pretend that all your contributors are immune to use case creep, deskilling, hype, "ai" psychosis, etc. 1/🤮 #incus #incusos #slop #slopware #vibecoding
48
3
29
0