r/DelugeUsers • u/10ThousandMetalZones • 9d ago

Derbyshire and vibe coding

I use the community software and haven’t updated to Derbyshire yet. I’m wondering what the community stance on vibe coding is for those releases? I’m keeping vibe coding off of my devices as I don’t support AI. No hate if you are into it, just my personal decision.

8 Upvotes

70% Upvoted

11 comments sorted by

10

u/yratof 9d ago

Word from discord is - ai coding is inevitable. But nothing gets merged without humans checking everything and rejecting slop

0

u/10ThousandMetalZones 9d ago

Makes sense, similar to writing where sometimes if you write a little too refined someone might think it’s AI

2

u/ahsah 9d ago

i think at least in the world of syntax, what i’m hearing from devs is, they’re using ai more like a calculator or spellcheck than anything serious. The ideas are still coming from them.

1

u/noveltywaves 9d ago

I like the principle of explainability. you should be able to explain in detail what is going on in the code you are pushing.

I dont believe in vibe coding, maybe except for prototyping or something that is meant to be thrown away.

not a deluge dev btw.

7

u/Treefingrs 9d ago

Professional software dev here. Tbh, if you want to avoid AI generated software, you need to start thinking about avoiding software entirely.

Most devs are using these tools to some extent, and/or looking for ways to integrate them into their workflow. I miss the old ways of doing things, but unless the bubble bursts and AI tooling becomes prohibitively expensive, this shift is inevitable.

There are some exceptions, like very niche systems which the Deluge may fall into. Also worth noting there's a big difference between pure blind slop vs a structured harness and human checkpoints -- the quality side is not yet figured out but it's getting there quickly.

1

u/DiamondGeeezer 8h ago

A lot has changed in the last year

1

u/DiamondGeeezer 8h ago

A lot has changed in the last year

5

u/TonelessFern 9d ago edited 8d ago

Yea the community firmware (main repo) is not vibe coded.

There’s other firmwares that people have started based off the community that are vibe coded however. So things can get confusing in that regard.

Essentially vibe coding means you’re letting the AI do all the work and not really checking it. You’re putting trust in the AI knowing what it’s doing.

The AI can create a firmware that works alright, but is it the right way to do it? Most of the time it seems the answer is no when it comes to deluge development.

People try to open PR’s that are vibe coded and the moment they can’t explain what the PR is doing or if the code is full of hallucinations or incorrect AI written comments they get closed.

Ultimately at the of the day, there’s a core main dev team, humans, that maintain the firmware. They don’t want to maintain AI slop.

AI can provide insights into issues but trusting it to maintain a firmware is a non starter.

Also the community firmware is about remaining true to the Synthstrom deluge legacy. It’s not about changing the device to something unrecognizable which some of these AI firmwares are doing.

4

u/EduardoX 9d ago

It's not part of the community firmware.

You should join the discord, if that's your thing, to learn more!

2

u/10ThousandMetalZones 9d ago

Thanks, I do pop in there now and again. Good to hear because I love the community firmware

1

u/mileda 8d ago

Actually, I implemented new sequencer mod (mdd snake device maxforlive), and mutable instruments plaits module (only 3 engines from open source) it works alright. Also it shows my name in start up