Elephant in the room? Not really!Ivan_C wrote: Wed Apr 22, 2026 5:05 am Let’s talk about the elephant in the room: is it going to be a KVR vibe coding challenge?
"Vibe coding" – that is, letting the AI do the coding – only works
for small projects. It's good for quickly "taking a look" and
prototyping.
But VST plugins are supposed to work, be maintainable, and
extensible. And that's not possible with "Vibe coding." Try it out!
With Vibe Coding, the AI suggests code that is almost always
unstructured and barely understandable. For the developer of a
plugin, the code thus remains a "black box." The developer
doesn't know exactly what each line of code does and why.
Therefore, the developer cannot add corrections or extensions
— the code is unmaintainable!
The beauty of plugin software development is "how you develop
the functionality right from the start" and see the project grow
slowly step by step, and you write and develop every single line
yourself. The developer understands every single line, can
correct, extend, and improve the code at any time. That's very
satisfying. But none of that works with Vibe coding.
But of course: Many will start with vibe coding and (unfortunately)
completely fail. Pure vibe coding isn't suitable for a finished,
good VST plugin.