[sdiy] AI code generation

bbob fluxmonk at gmail.com
Thu Apr 23 13:08:28 CEST 2026


I am a retired analyst/project manager, and I’ve found my experience
writing specs for programmers to be a perfect skill set for writing AI
prompts.

On Thu, Apr 23, 2026 at 7:03 AM Mike Bryant <mbryant at futurehorizons.com>
wrote:

> In the mainframe days there were programmers and systems analysts, and the
> analysts tried to define the problem space adequately for the programmer to
> create an error-free program.
>
> So now we're all systems analysts 🙂
> ------------------------------
> *From:* Synth-diy <synth-diy-bounces at synth-diy.org> on behalf of Tom
> Wiltshire <tom at electricdruid.net>
> *Sent:* 23 April 2026 10:42
> *To:* Brother Theo <brothertheo2014 at gmail.com>
> *Cc:* synth-diy at synth-diy.org <synth-diy at synth-diy.org>
> *Subject:* Re: [sdiy] AI code generation
>
> I've also had similar experiences with Claude doing something that would
> have taken ages in only a few minutes, so these tools are here and thy#re
> going to be used and if you want to be a "modern programmer", you're going
> to be using AI assistance in one way or another.
>
> That said, I've also had experiences where Claude produced stuff that
> simply wouldn't work and was wrong in fundamental ways. You absolutely have
> to check and you absolutely need to make sure you've got good code
> verification and debugging in place.
>
> Computing and programming has always been a fast-changing world requiring
> constant re-skilling to keep up, and that's still true now. Stand still and
> some new kid who just learned the new tools will get the job instead of you.
>
> > On 23 Apr 2026, at 10:14, Brother Theo via Synth-diy <
> synth-diy at synth-diy.org> wrote:
> >
> > Hey everyone,
> >
> > Touchy subject that I need to talk about. I just had Claude AI generate
> a CSound program for a complex effect. Not only did it hit all the points I
> gave it, but it even included some stuff I forgot, like a sound source, but
> also gave me a few ideas on how to operate it. And it took less than 15
> minutes to do.
> >
> > I know a lot of you will rebel against the idea of AI. I was one of you.
> But this experience has opened my eyes to the possibilities. This piece of
> code would have taken me hours to develop. Claude did it in a fraction of
> the time.
> >
> > My buddy got me into this by telling me his experience. He took a code
> base for a 2007 synth and had Claude make changes and add features. Claude
> even found bugs and fixed them without prompting. The new code is working
> and is being tested.
> >
> > It is a brave new world. Should we feel sorry for the coders?
> >
> > --
> > Timothy Ressel
> > 909-423-5962
> > FutureRetro Synthesizers
> >
> > ________________________________________________________
> > This is the Synth-diy mailing list
> > Submit email to: Synth-diy at synth-diy.org
> > View archive at: https://synth-diy.org/pipermail/synth-diy/
> > Check your settings at: https://synth-diy.org/mailman/listinfo/synth-diy
> > Selling or trading? Use marketplace at synth-diy.org
>
>
> ________________________________________________________
> This is the Synth-diy mailing list
> Submit email to: Synth-diy at synth-diy.org
> View archive at: https://synth-diy.org/pipermail/synth-diy/
> Check your settings at: https://synth-diy.org/mailman/listinfo/synth-diy
> Selling or trading? Use marketplace at synth-diy.org
> ________________________________________________________
> This is the Synth-diy mailing list
> Submit email to: Synth-diy at synth-diy.org
> View archive at: https://synth-diy.org/pipermail/synth-diy/
> Check your settings at: https://synth-diy.org/mailman/listinfo/synth-diy
> Selling or trading? Use marketplace at synth-diy.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20260423/90c5ff29/attachment.htm>


More information about the Synth-diy mailing list