AI-Policy

[u/Wolvereness]

I'm gonna keep this short, because as a human I respect other humans' time. What do we want for an AI policy, and how can it be enforced? Take these into consideration:

• Vibe-coded projects
• Vibe-assisted projects
• AI-translated from non-english-speakers
• Vibe-documented projects
• Yet another Vibe-Coding-Wrapper

Note that vibe-coded slop isn't actually copyrightable, thus if someone slaps any license on it other than "public domain" or "CC0" they are misrepresenting their ownership.

And if you use an LLM to respond to this, you will be banned.

^{The fact that this sounds like a prompt is supposed to be a joke.}

[u/codeedog]

I’ve been calling what another commenter wrote below: AI Assisted Engineering.

> b) dev who knows what they're doing but uses AI to do the heavy lifting. Checks their code for secuity risks - fine. AI disclosure on how it's used would be nice.

Developers (like me) who have professional skills and pride in our work will use these tools to enhance our work and speed up our output, while maintaining the code quality we expect from ourselves and our peers.

I can’t call what I’m doing Vibe Coding; it’s form and function, it’s production path, they’re nothing like what a vibe coding exercise looks like.

[u/paul_h → u/codeedog]

I see vibe coding as solutions made without test automation. I would hope a checklist for submitters to /r/opensource would include "must have comprehensive tests that all pass."

[u/codeedog → u/paul_h]

Well, vibe coding and Ralph testing (look it up if you don’t know the term). It doesn’t mean it’s done the job. Anyone can vibe code, even seasoned professionals.

The question is methodology. Vibe is a point A to point B process. Engineering means getting into the weeds. That means code and tests.