I’ve had basically no luck getting code from the chat-style interfaces, though. The bugs often aren’t even subtle, and it’ll either argue with me that there’s not a bug or apologize and produce exactly the same code again.
But typing is like less than 1% of the time spent programming, it doesn't take many seconds to type the things you mentioned and it takes significantly longer to figure out you want to make them.
We had to develop something internally regarding genlock and a ring buffer that Python wasn't going to work, so an engineer at our company picked up C++. Mind you, he's never written a line of C++ in his life and has close to no experience with C-style languages at all.
Within 2 days he had completed the prototype to synchronize multiple latency sensitive gear with leading/falling edge methods in C++. (On top of his other work.)
3 days prior to it he'd written no C++.
When asked how he did it, he said: "Claude is the best translator out there."
As for subtle mistakes, you still need to know how to code. Compilers make plenty of subtle inaccuracies and we still use them for most applications, don't we?