This board needs a "Vibe-coded" prefix

[linkenski]

You know?

 

[Reploid]

wut

 

[purple_bandit]

Chad-coded prefix

 

[mathew77]

Yeaaa, agreed!.. Kill all hoomans! Bite my shiny metal ass!..

 

[ChibiMofo]

Wouldn't it be better and more humane if we just instabanned "developers" that post that shit?

I mean I think it would win a poll here.

 

[smileyhead]

Would people use it, though? Also, a more general ‘AI-assisted’ prefix would be preferable IMO, so that it covers more than just coding.

 

[spinal_cord]

LOL, no. By that sense, we need specific "BASIC Coded", "C Coded", "ASM Coded", "Read it in a book some place Coded" "Googled it Coded" etc.

 

[smileyhead]

LOL, no. By that sense, we need specific "BASIC Coded", "C Coded", "ASM Coded", "Read it in a book some place Coded" "Googled it Coded" etc.

Generally speaking, AI disclosure isn't about telling people in detail how a project is coded under the hood. It's more like saying ‘Hey, I probably don't understand how exactly this works, code quality is likely poor, and I don't plan on maintaining it well – or at all. It seems to work, but use at your own risk.’

 

[spinal_cord]

Generally speaking, AI disclosure isn't about telling people in detail how a project is coded under the hood. It's more like saying ‘Hey, I probably don't understand how exactly this works, code quality is likely poor, and I don't plan on maintaining it well – or at all. It seems to work, but use at your own risk.’

A disclaimer I should have an everything I hand coded over the past 30 years. Literally 10 minutes after coding something I have forgot what the hell I was thinking. Go on, ask me how DSision2 or DiagnoSe works...

 

[The Real Jdbye]

Generally speaking, AI disclosure isn't about telling people in detail how a project is coded under the hood. It's more like saying ‘Hey, I probably don't understand how exactly this works, code quality is likely poor, and I don't plan on maintaining it well – or at all. It seems to work, but use at your own risk.’

Really no different from coding by googling what you want to do and copying the first stackoverflow result in that sense.

 

[Lostbhoy]

Maybe best to put this in site suggestions.

Not sure it will fly tho as previously mentioned, not all devs are full time super qualified experts at every code or tool used so it would mean a prefix for everything.

Maybe, just a disclaimer about how something was developed is really upto the dev themselves but why does it matter except for vibephobes?

If it works, it works...

 

[Mayo1990]

If we get a Vibe coded tag, I also want a StackOverFlow tag.

Wouldn't it be better and more humane if we just instabanned "developers" that post that shit?

I mean I think it would win a poll here.

I also use AI for coding (although I do have programming fundamentals myself, so It's not entirely a blind run, and I also check if whatever It's spitting makes sense) but since the entry bar for homebrews has become quite low in general It's good to have a rule that shows a product that is at least 70% done or with a release. As time goes on the risk of seeing this forum flooded with projects that don't reach a playable stage is pretty high, given how good AI is turning at coding.

Would people use it, though? Also, a more general ‘AI-assisted’ prefix would be preferable IMO, so that it covers more than just coding.

Honestly an AI disclosure per release rules is good. But that may turn everything into a witch hunt where someone may deny that they used AI and then someone else will point out the opposite either for spite or because they lied to begin with.

Maybe best to put this in site suggestions.

Not sure it will fly tho as previously mentioned, not all devs are full time super qualified experts at every code or tool used so it would mean a prefix for everything.

Maybe, just a disclaimer about how something was developed is really upto the dev themselves but why does it matter except for vibephobes?

If it works, it works...

I hope no one uses Linux if they think AI is bad.

 

[TheStonedModder]

If we get a Vibe coded tag, I also want a StackOverFlow tag.


I also use AI for coding (although I do have programming fundamentals myself, so It's not entirely a blind run, and I also check if whatever It's spitting makes sense) but since the entry bar for homebrews has become quite low in general It's good to have a rule that shows a product that is at least 70% done or with a release. As time goes on the risk of seeing this forum flooded with projects that don't reach a playable stage is pretty high, given how good AI is turning at coding.

Honestly an AI disclosure per release rules is good. But that may turn everything into a witch hunt where someone may deny that they used AI and then someone else will point out the opposite either for spite or because they lied to begin with.



I hope no one uses Linux if they think AI is bad.

View attachment 582131

If some of these “ai bad” folks spent less time complaining about something that’s clearly here to stay for a bit, and learned the tools themselves. Imagine how much farther ahead the community would be

I understand the nuances and why folks dislike the use of AI. But at this point it seems like the loudest ones about it are the ones least affected and that don’t use or have ever used it

 

[Mayo1990]

If some of these “ai bad” folks spent less time complaining about something that’s clearly here to stay for a bit, and learned the tools themselves. Imagine how much farther ahead the community would be

I understand the nuances and why folks dislike the use of AI. But at this point it seems like the loudest ones about it are the ones least affected and that don’t use or have ever used it

The "ai bad" folks are half right, and half wrong honestly.
I perfectly understand someone who has no idea what they're doing touching other source codes, while at the same time I clearly understand that a lot of those only see the rushed out homebrew ports made by AI that clearly didn't go through multiple debugging sessions on real hardware. But yet again, if the end product is perfectly working, passes all the checks and people won't touch it "because AI was involved", they weren't gonna touch it to begin with.

I dislike AI when it comes down to generate images, videos, voices and such. But for coding? It's a great tool. For debugging? My hands and my brain are right there as well all the documentations I need to work on something. Not really that different from opening Stack Overflow back then and stealing whatever you had to steal to make it work in your codebase.

Banning vibe coded or AI-made homebrews is also not a viable option because people will just stop saying that they used Codex/Claude/whatever and it will turn any homebrew project into a witch hunt. But having some additional rules where people have to prove that whatever they're working on works on real hardware (emulators aren't a good metrics, like at all, to show that your product is working) and is at least 40-60% done is something I'd gladly take as AI becomes very viable at developing homebrews.

 

[Exnor]

I use "AI" for some personal projects that i store on GitHub. I always disclosure the usage and the name of the LLM model and version.

Its just good practice, since i'm not an expert (or even talented) coder, and this code might have some vulnerabilities that i am not aware of.

Is "AI" coding bad? I don't think so. LLMs/DL are great tools for coding (and learning), but without an expert looking at the code to vetted it and give it an "its ok", we should disclosure the use of "AI".

Just my 2 cents on the topic.

 

[Scarlet]

I feel dirty using it. I wanted to try Fable before Anthropic gated it behind buying tokens, and holy shit can it do some good stuff. AI really is one of those things that could be so great if it wasn't like, ruining people's lives and destroying the entire technology market.