Anyone else noticed the increase of Vibe coded plugins flooding the market?

[ksandvik]

The AI Center tech bros are now putting their eyes to countries with plenty of water, cheap electricity, cold climate and local politicians duped to believe they get a lot of new jobs.

[D-Fusion]

The AI Center tech bros are now putting their eyes to countries with plenty of water, cheap electricity, cold climate and local politicians duped to believe they get a lot of new jobs.

Yep. We are in for a very bumpy ride.

[jamcat]

Just to understand what we're actually talking about. This is the claim that kicked off the data center fear and loathing. It overestimated water usage by 1000 times because journalists don't understand math.

Last month, journalist Karen Hao posted a Twitter thread in which she acknowledged that there was a substantial error in her blockbuster book Empire of AI. Hao had written that a proposed Google data center in a town near Santiago, Chile, could require “more than one thousand times the amount of water consumed by the entire population”—a figure which, thanks to a unit misunderstanding, appears to have been off by a magnitude of 1,000.

https://www.wired.com/story/karen-hao-e ... statistics

Here is the research writer that exposed the error:
https://andymasley.substack.com/s/ai-an ... e?sort=top

[El°HYM]

World*s most renowned Vibe Producer with his thoughts on Vibe Coding and becoming it's unofficial Mascot.

Great indeed is the sublimity of the Creative, to which all beings owe their beginning and which permeates all heaven.

Lao Tzu

[jinxtigr]

It seems to me the talented devs (I hang out with some) get to run with this stuff, if it meets their moral/ethical standards (note: we are in the music business) and the good ones continue to act very much as themselves but maybe have upped their production.

I don't think this is the AI actually helping them. I think it's just enticed them to go on a tear. I went on a tear with the new Meter without any AI involved at all: just started doing stuff and trying the next new idea, and typed 'em all out myself. I think talented coders get suckered into going on a tear when the AI seems to be 'writing code for them, but imperfectly' and they're just trying harder, for as long as they're happy doing so. And that's the talented ones.

And then there are some who fully go mad and think the AI is giving them godlike powers, and also start replying to every possible thing, and it's always 'the bug is being fixed, that problem isn't real, it's great, note my positive cheery tone with lots of emdashes' because they're using AI for EVERYTHING and don't have the sense to recognize when they're acting inhuman.

And then there's always some who go fully psychotic and come to grief because they're gambling their real lives on the idea the AI will meld with their simple ambition to become a Voltron of tech total dominance, and it's their aggression that kind of sidelines those folks: they get mad when you don't admit their superiority and it becomes a fight and they're using the AI to do the work for them but aren't using it to couch their PR in marketing-speak.

We really are seeing all kinds. You might not spot the talented guys with experience doing it because, like I said, I think they're just on a tear, as themselves. It saved them a lot of typing (at a cost, even if only the vast sums they're now paying for tokens) but they're still basically coding as themselves, just tricked into working lots faster than they were.

It's weirdly encouraging that lots of people are finding ways to faceplant at AI speeds, rather than work at a normal rate. It's pretty harrowing how much they're flooding the zone, though. And I say that as a dev known to go too damn fast and always have

[Funky40]

i`m chatting with chatGPT -> it`s absolutely amazing !

you just have to ask the right questions !
and: i told it too keep it short....and: it can (to some extent )


checking waters right now vs. many small details vs. my plugin ideas.
whats effectivly in reach vs. a simple AI-assistent ? specific feature details
- possible ? not ?....quality ?


the outcome:
- for anything in the field of what i want to create for myself (all: audio buffer related stuff)
- is the major key: to create a clear concept
- phrase ANHYTHING out absolutely properly
- learn to think how the machine has to think vs. data (in that case "Audio-buffer" data)
- specifie things out to detail ->AND: eventualities !!
- do NOT leave a machine alone with eventualities and a unclear situation ! haha
- means more code, and funnily, means higher securtity vs. crashes


conclusion so far after three chatBot chats:
- ANYTHING i was dreaming of to have for myself should be easily in reach (function and code wise) just based on me doing a vibe-code job. No access to data bases or repositorys required.

- KEY IS: clear specification, clear concept, clear wording, no left out info
- i can even ask it if i missed out any crucial information


- by asking my chat-bot questions do i effectivly already learn how later to talk with the AI-assistent. chatGPT also...i go for now with that (low level) AI....and might apply to Claude later IF i once have suceeded with a finished (personal) running plugin

i make first: a simple delay.......with a simple twist /very simple / very easy to implement /very effectful

but i`m talking already about a live-jam sample player, muahaha


ahh wait, the reason in post right now:
- i start now to see how low level work alots of devs actually are doing. Absolutely unbvelivable


- ALOTS in this field is definitly NOT a thing of high coding skills ! ->
- in contrary: ALOTS vs. my specific field is much more a thing of a high actual "music-making" understanding. live-jam stuff in my case
- a main thing it takes IS: to be able to see a specific functional idea in a real live-play context *while* you have NO product at hand, only your phantasy
- alots is based on actual visualisation capabilities -> and this vs. live-play / jam usages


- it`s about the understanding of what features will make it great, setup, values, control curvatures, visual feedback, live-jam access......small details vs, anything of those.
- the more you know any of these stuff already into precise detail, the more can a AI-assistent do for you
- you just have to be able to word out EVERYTHING with high clarity, precision and detail

- in my case, all functionalities are plain (simple) math.
- it`s all just: handle the content of an audio-buffer in this or that way
- "that" does not require any higher coding skills


i think it looks great for me -> in case i can make it thru all the first hurdles / made several steps yesterday / but that aspect is much harder than initially anticipated.


i see now a HUGE potential in vibe coding !
-> though, all these new kids and old men turning "that" into attempts of just cashing in -> is a very own topic "within all of that" /many topics within one


make a "product" rather than just a plugin for a few people ? NOT SAME


i see all your points you guys in the knows are doing.
But you guys are overdoing it for my taste with your: ".....but a good coder....."talks.

First comes the musician.....at least for all the stuff i am missing on this market.
jam-play stuff

First comes the musician with ideas phrased out into sheer detail.
That`s how i see it

see ya........need to work, haha

[Zeisner]

How can one identify vibe coded software?

What are the telltale signs?

The GUI and the webpage (if there is one) gives it away before the sound does. Nothing looks as if any effort, thought, knowledge, experience and taste has been put into it and there are artifacts everywhere. Just the text already gives it away ("I've been making music/mixing/mastering for 30+ years and decided to make my own much better plugins"). There's also more buzzwords to be found than usual ("Stochastic erosion"). Or the text has been entirely generated by AI in the first place.

[MJACau]

'Stochastic erosion' that's a wild plugin XD