I'll bite. I've been writing music for decades but I can't sing. With ai I can write lyrics and generate ai vocals, then separate the stems and extract the vocals throwing away the rest.
Add the vocals to my daw and create the rest the way I want.
Saying its a great work of art is subjective, but for me I can make music I couldn't before now.
Sidebar: learn to sing. Singing well and “finding your voice” are in my mind equivalent. Every time I become a more confident person I get better at singing. Every time my singing gets better through practice I feel more confident. “Speak with your chest” didn’t make sense until a few years ago. Now it’s obvious to me when someone is incapable of it.
So this is the classic tension between the "coding for the love of code" vs the "coding to solve problems" mindset. This cultural concept has been around since before AI was on the scene, heck well before software existed (craftsman vs builder).
I'm curious why this is a vs and you have to pick both? I've found coding for the love of code always helped me accelerate my speed and ability so that I could also deliver solidly on time and solve the problems too.
Ya this has been my sentiment. If i need to one-off a quick script that does some processing on data, it’s nice to offload that so i can focus on pieces of my code that are more important and interesting to me. The context switching cost is still there tho…