Unser nächster #Java Usergroup Termin steht bald an.
@sparsick erzählt uns alles über schmerzfreies Aufsetzen einer Dev Umgebung
https://events.ijug.eu/events/ccbd5f78-1e7e-4a05-977e-c6041b8bf61a
ZDnet headline: "I tried a Claude Code alternative that's local, open source, and completely free"
I, too, am using an alternative that is local, open, and free. I write my own damn code, instead of asking for slop from a so-called "AI" plagiarism machine trained on stolen code.
#AIslop
Quoting Gabriella Gonzalez @GabriellaG439 on #vibecoding:
[…] This example is pretty representative of my experiences using vibe coding. Every time I try out vibe coding for real (and not for demos) I start out feeling hopeful and excited and leave feeling let down and disappointed. I don't want to produce throwaway code: I want to build things that will last and won't blow up in my face later and I don't want to handhold/babysit/cajole the tool to get the results I want. I want vibe coding to improve the quality of my work, not deteriorate it.
https://haskellforall.com/2026/02/my-experience-with-vibe-coding
@brouhaha I wish more people, like yourself, will highlight the unethical aspects of ai not just technical and how far reality is from the hype.
Imho Statistical pattern matching can produce code or prose, for sure, it’s just not fit for purpose when there’s a specification, quality control and any type of audit to verify what’s produced. It’s a terrifying mess and I’m merely using it to configure #emacs 😊 the time wasted and amount of slop produced to make even the smallest change is pathetic.
I recall seeing it processing all my checked-out 3rd-party libraries when I asked it to change a value of some configuration option it could have simply read the docs describing it in an emacs it had full access to with an MCP tool. You often have to write very specific and elaborate prompts; you might as well just learn elisp and write the code yourself.
Similar experience with #Nix here https://kolektiva.social/@oatmeal/116003504003556422
Thanks!
Quoting Gabriella Gonzalez @GabriellaG439 on #vibecoding:
[…] This example is pretty representative of my experiences using vibe coding. Every time I try out vibe coding for real (and not for demos) I start out feeling hopeful and excited and leave feeling let down and disappointed. I don't want to produce throwaway code: I want to build things that will last and won't blow up in my face later and I don't want to handhold/babysit/cajole the tool to get the results I want. I want vibe coding to improve the quality of my work, not deteriorate it.
https://haskellforall.com/2026/02/my-experience-with-vibe-coding
