I enjoy learning about the design philosophy behind an API, or diving into a library to learn the "off the beaten path" workflows. That's where the magic optimizations or shortcuts live.
So far, copilot just shows me the happiest path options for everything I've tried, and really falls over when it's not something that "Well this API looks like API_functionCall, so your query for <get X> must look like API_getX". It rarely does.
Slightly related - there was a Reddit post about a person lamenting the changes in their job. [0] They make 3D models and they greatly enjoyed making models from scratch and taking 2-3 weeks to do so.
Now with AI, they use tools to create a model - and then spend 2-3 days to update it.
This is a productivity improvement, but it also took away a key thing they loved about their job. There isn't really a solution here at all, and the poster wasn't looking for solutions either. Just venting.
We'll be seeing this more in the future, and I wouldn't be surprised if multiple people change careers over it.
So far, copilot just shows me the happiest path options for everything I've tried, and really falls over when it's not something that "Well this API looks like API_functionCall, so your query for <get X> must look like API_getX". It rarely does.