• 9 Posts
  • 490 Comments
Joined 11 months ago
cake
Cake day: August 25th, 2025

help-circle






  • I love that, and would absolutely welcome it.

    I actually have a repo at codeberg up where ive started moving the rules and things for public access/visibility, and thought that a wiki could go there (and be easily brought elsewhere if needed without any intervention needed by me).

    Even if was just links to resources we could post up, whatever.

    I’d be happy to spin up another repo just for wiki use and link it in the sidebar. The big issue is, of course, the content itself, so we will need some folks to contribute.

    But if its an interest I can get this started in a few hours (summer sports for the kids, probably not going to be home for more than a few minutes for about… 4-5 hours)











  • Yes, because it is a bit different than a search engine. It may not be changing the files, but it is telling you the way to do it. It might give you an outdated method/pattern, it might ignore conventions, and most importantly, it doesn’t really understand the problem its solving. Its not finding the optimal answer, its finding the most common.

    So the resulting answer may work, but not necessarily be right. In a disclosure (see the new thread) that would be referred to as “hint” for lllm use.

    That doesn’t mean the answer you got was necessarily wrong either, just an answer based on an amalgam of the most common for all the code fed into the model, no matter when the code was written.

    It would be put into an ai disclosure, so it qualifies for a tag. Make sense?



  • None of this is specifically about you, FYI.

    There have been a good number of posts, and there are some people very solidly anti AI anything, some who use it as a tool, and some who use it for everything. That combo meant we need rules about it - in addition to the rules about account age and f/loss exceptions and the like.

    Edit: For the record, the 100% vibecoded app I tested was posted by someone else.