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

help-circle







  • 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.





  • I’d love an idea to trim it down… but with the wide varieties of ways AI can be used, its hard.

    I’m a good example of the “problem” person in a way. I’ll test all kinds of things (including a completely, 100% vibe coded app posted here recently… in a sectioned off vlan of course), but what AI was used for influences where I look. Documentation? Ok, not the worst, but I’m going to check for human review/blatant llm goofs. You used it to figure out how to talk to a serial controlled endpoint? Ok, thats what needs to be checked first.

    You made the whole ass thing with Claude? I’ll test it like I said, but I doubt it would ever end up anywhere near my own production use, its more as a curiosity. 99/100 that level of generated is basically the same as calling it unmaintained imo.

    So there is definite value to knowing where/how/how much, and if the comments consist of things already stated and just add “slop”, thats going to get deleted, its already disclosed, the people who comment that should filter instead. Its a two way benefit this way as I see it.

    That said - I’m always open to options here, but considering recent comments and reports since I’ve taken over moderating, something is definitely needed.

    Edit: And just to mention - nothing is ever set in stone, if you’ve not seen my other comments about it. Should anything change, or it becomes unwieldy, or someone finds a workaround to abuse, whatever - its always open for discussion.


  • Disclosure itself is a need, and I can confidently say there are enough people who are “no ai ever”, “all ai all the time”, and “only the AI use I agree with” to make something needed.

    About the only way to simplify would be to not define the disclosure types, just to disclose it, but then half the post will be discussing where and how if its not defined (along with a bunch of reports about not fully disclosing AI use).

    If promo posts included that up front, I don’t think it would be an issue, but its rare that any post includes even “I used/didn’t use AI”, if that.








  • You’d be wrong.

    The fields aren’t all the same kinds of values, which requires relationship between the data to be evaluated for entry.

    You’re assuming this is transposing contents, which was not the issue. Your example is what was initially planned and halted before transitioning to the approach I helped deploy.