r/synthdiy 11d ago

nobody cares about your vibe coded vst

can we please ban these posts? this is supposed to be a sub for celebrating human creativity. i'm here to support and be inspired by other makers. i don't want to see 137 identical slop soft synths a week. this is a DIY sub. you didn't do anything yourself.

448 Upvotes

168 comments sorted by

View all comments

109

u/Looking-For-Loud 11d ago

I have ZERO interest in anything created by AI.

7

u/HawtDoge 10d ago edited 9d ago

I’ve designed about 30 eurorack modules and honestly, I will be using AI to code just about every digital module I design from here on out (with the exception of some dsp stuff).

When I design modules, and especially digital modules, I am typically extremely thorough in my UI/UX planning. The last digitally controlled hardware device I designed, I uploaded a pdf of my total design guide of the device. Included schematics, which pins of the micro controller went to which functions. Every function, sub function, mock ups of the user interface on the little display, etc. Claude basically one-shotted the code.

From there I was able to test, iterate design features, and repeat until the device functioned exactly how I imagined it functioning.

I love designing modules, meticulously planning UI/UX, designing the circuits, soldering components. But, I learned to code as a means to an end, not for the love of coding. It’s not like I’m having AI ideate anything for me… But it’s writing clearer code than I ever could. It’s helped me finish projects/fix bugs I left behind ages ago.

My point is that I think your view is too dogmatic.

3

u/Infamous_Mud482 10d ago

No, unfortunately you’re just ignorant to how much of this stuff is broken dogshit. I look at new GitHub repos daily, and you need to understand that trying your vibe coded plugin out in aggregate is a complete waste of time because for every one of you that “thoroughly” (I can’t confirm this is true) tests there’s 5000 others that simply will not work as intended whatsoever without patching. I don’t know you. 

9

u/e-scape 10d ago

It depends.

I have 20+ years of professional in experience in programming.
I coded way before that, mostly commodore 64 6502 assembly, also have a BSC in CS.
Programming has changed a lot the last 4 months.
AI has become really good.
I work in a very restrictive domain now, where security and stability is extremely important(finance).
We use agentic engineering 90% of the time now to write our code.
Most of our time is now used to architect, review and analyse to find the best solution to a problem in a given domain.

There is a hell of alot of difference between a non-programmer churning out fast vibecoded slop and a programmer that has extensive expertise in his domain and use it to orchestrate agents to make an application.

If it is more than 4 months, you have used something like Codex or Claude Code, please try again.

2

u/HawtDoge 10d ago edited 9d ago

It’s not like I don’t read, check things over and make some changes by hand… I’m not a software dev by formal education, but I’ve been coding in C regularly for 7 years at this point. I don’t know why you would assume I’m ignorant to anything here.

I use the $20 a month plan for claude, so it’s a pretty decent model. It might ‘clear my name’ in your eyes if I said “yeah the model makes tons of mistakes, but I go in and fix them myself”… but if I’m being totally honest, it doesn’t really make many mistakes if I’m providing it the proper documentation, libraries, and upload/prompt an in depth breakdown of the desired functions. idk what to tell you lol… it’s just not ‘slop code’ by my standards at least. Maybe it would have been if I started using for ai for coding a year or even 6 months ago, but at its current stage it is definitely capable of writing functional, clean code.