I've got one. I'm working on a cryptographic identity system in rust. One of the stricter iterations of it demanded creating a public version and private version of each type. The best way to accomplish this is a procedural macro. I don't know if you've written proc macros by hand in rust. I have, years ago, and it was somewhat torturous. I didn't want to relearn to do it all over again and spend what would have taken weeks (this is a side project) to gain a skill I will easily forget in a month or so. So I had an LLM code it for me. This is a really great use for it: it's not building any strong logic or doing any IO, it's simply writing code that generates other code, and is entirely verifiable and testable. It built it for me so I could spend those weeks working on higher level logic and p2p syncing protocol stuff that actually matters for the project.

I want to make it clear that I'm an LLM luddite. I mostly find the things distasteful and obnoxious. But there are definitely use-cases where they can do what's essentially bitch work and save a lot of time that would otherwise be a waste. It's a tool that can be used for specific things. I don't use them for everything.

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.

Exactly. What service got better and/or cheaper?

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).