I found that Copilot was much more helpful when you write 'companion' code.
Take for example, you're writing two functions to make a GET and a POST request to an API. When you write the first GET request, it knows nothing about the API you're using or how you might want to use it. So you essentially need to write it yourself.
But then when you need to go and write the POST, it has the GET call as an example. Now it knows about the API and vaguely how you are going to be making the calls. You can almost tab complete the entire thing and just make a couple of changes to the parameters.
I found that using COPILOT with this mindset really takes advantage of its learning ability. It does pattern recognition, not mind reading.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I found that Copilot was much more helpful when you write 'companion' code.
Take for example, you're writing two functions to make a GET and a POST request to an API. When you write the first GET request, it knows nothing about the API you're using or how you might want to use it. So you essentially need to write it yourself.
But then when you need to go and write the POST, it has the GET call as an example. Now it knows about the API and vaguely how you are going to be making the calls. You can almost tab complete the entire thing and just make a couple of changes to the parameters.
I found that using COPILOT with this mindset really takes advantage of its learning ability. It does pattern recognition, not mind reading.