I actually used it for the first time tonight. I was about to do some C coding, double buffering, etc. etc. to calculate in db the signal level of some audio.
It's not that I needed ChatGPT to tell me how to do these things, but as something you can run questions by and have it spit out code is actually useful. I also like how you can stop it, redirect it or rephrase your question and it remembers the context.
Like I stated to it. "I want to do double buffering in C"
It went off on a tagent about graphics double buffering and gave me an example of the SDL framework.
So I stopped it and said, "No I mean general double buffering"
And then it gave me a much more appropriate answer and code.
Same thing for asking it about audio energy calculations, rolling averaging windows and reduce down resampling.
Again it's not that I needed ChatGPT to give me that code and to be honest, the only bit I copied verbatim (and actually needed to look up) was the conversion to db.
It's just that it provides an interesting sounding board. For example, "I need a queue, I can reorder", you could hmm and haaa and think of 6 different ways of doing it, and/or you could ask ChatGPT and see how close it comes to your thoughts and help sway you one way or other. It might give you the solution you know won't work this time, but tell it that and see what it comes up with next. I found myself nodding and saying, "Hmmm, yea, that works. Except maybe...."
As to generating code snippets to save you typing them. Meh. It's probably faster to type them out that fix what you C&P from ChatGPT.
It leaves open the question of... how do you spot these in interviews. If the person can literally have you question "speech to text" and sent to ChatGPT live.