I would agree that it is probably easier than you think to code a VCV Rack plugin, half the battle is understanding how they work.
And using AI to generate code so that you can learn how plugins work is a good tool.
Although, I would not like to see a proliferation of AI generated junk plugins added to the library! By all means use AI to help you write code, but please don’t expect AI to help you out with all the UX work, debugging and/or testing, and all the polish and finishing touches that a “good” plugin should get before it is submitted to the library…
Don’t get me wrong, I would love to see more plugin developers, more ideas, more cool modules, endless possibilities.
I am finding it harder these days to carve out the time to work on my plugin (day job, irl responsibilities etc) and I also find that after an extended break from development, I often forget some critical bit of my workflow and find it hard to get back into the swing of things…
So I decided I would document how I develop my plugin. Initially I just wrote notes to myself, but I eventually realised, you have to write documentation as if it is for someone else, only then can you be sure that it actually contains the things you might need to recall in the future.
So I started to write the documentation in a GitHub repo just in case I ever wanted to share it.
Unfortunately I haven’t found the time to finish this either, BUT maybe it could still be useful to beginners in some way, and maybe sharing this will provide some motivation to complete it at some point as well.
Small caveat that it may contain errors, but with that said, if you are interested, here is the repo: