346
Deleted (aussie.zone)
submitted 4 months ago by to c/selfhosted@lemmy.world
131 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 16 points 4 months ago (2 children)

What does it mean for a project to deserve the [AI] tag? This matters, because you may have a lot of projects where a developer may think "no" and someone else thinks "yes". Some examples from my day job:

  • Developer used AI to understand part of the codebase and suggest ways to accomplish goal. Developer incorporated that suggestion, though using their own knowledge deviated from AI's suggestion in parts. Developer wrote the code themselves. Is this project [AI] or [NOT AI]?
  • Developer used AI to review existing (human-written) code for quality and security purposes. AI noticed some issues and proposed fixes. Developer reviewed and accepted them. Is this project [AI]?
  • Developer knew they wanted to implement a feature, and while implementing it there was a boilerplate function. Developer asked AI to write this function, manually reviewed it, confirmed it worked, and added it to the codebase. Is this project [AI]?

In these examples the developer carefully reviews the AI's output, which I think distinguishes it from vibe-coded slop, which at least is what I want to ignore.

It's also worth noting that an open-source project may receive and incorporate a well-written contribution where the human developer used AI carefully like this. Unless they disclosed that they used AI, it may be unknowable to the project maintainers whether their project is [AI] or not, depending on how you define it. What tag should these projects use?

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 4 points 4 months ago

    @festus @selfhosted Excellent examples. What the tag [AI] conveys is not what you really need to know, which is the quality of the code (component/unit), unit testing, and so forth. I assume there is some acceptance testing done at the project level. The human who submits the code must understand that flaws in their code is their responsibility, just as those who contribute/maintain the project are responsible at the system level. It is both an objective and reputational process. Does it really matter what tools are used if the work product passes the test, verification and validation criteria? Sloppy code is not unique to AI tools.

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (-1 replies)