Yet it's extremely useful in various usecases.
"Mutate this code so it adheres to XYZ pattern"
"Factor this code out into a React component and wire it up"
"Tell me what this code does, what do I need to change to make it do XZY"
"I need to programatically access AWS <service>, guide me through AWS console to set up the right IAM policies and generate those for me, then generate the correct boto3 code to call this service"
"Take this email, write a friendly and brief response and ask for setting up an appointment next week"
"Write me a bash script that uses imagemagick to perform a bunch of transformations on image files with the following filenames"
"Take this curl command, turn it into a Python function, add type annotations and comments where necessary"
And many, many more usecases. Does it bullshit? Absolutely, but that's just not always an issue. A lot of the bullshitting can be circumvented by prompting it in the right ways and having the right discourse with it.
It's a room full of employees, and you are the manager. Will you hear plenty of bullshit? Absolutely, but you will also get heaps of useful output that can solve your problem, make you think outside the box etc. It's all about how you interact with it.
It's a significantly more pleasant and productive interaction mode than using a search engine and sifting through the SEO spam. I still do that, if I need to verify something or validate if something I don't have enough domain knowledge of is bullshit or not, but more often than not I don't need to. and that's been incredibly liberating.