In my experience, if I'm looking how to do something pretty standard with an API I'm unfamiliar with, it's usually correct and faster than trying to trawl through bad, build-generated documentation that would rather explain every possible argument than show a basic example.

And in the case it's wrong, I will know pretty quickly and can fall back to the old methods.

> Like economists, who have predicted 7 of the last 3 recessions, AI knows 17 out of 11 API calls!

It's definitely been said before, but the fact that they're calling out these non-existent functions in the first place can tell library devs a lot about what new features could be there to take up the namespace.

A tool that gives me 17 out of 11 API calls from a vague textual description of my intent would be incredibly useful.