This is my takeaway from using Copilot as well. Given my domain and language of choice, Copilot's suggestions range from non-idiomatic to completely broken when

This is my takeaway from using Copilot as well. Given my domain and language of choice, Copilot's suggestions range from non-idiomatic to completely broken when it comes to any kind of feature work. I don't think of it as a tool that solves problems for me, I see it as a glorified autocomplete that understands code and is skilled at applying patterns from previous lines (e.g. in config files) and other files in your project in a way that usually makes sense. This is a contrived example, but just to illustrate the kind of pattern matching I'm talking about, say I'm writing the following code: VAR_PROJECT_A_VAR_A=$(curl http://localhost/PROJECT-A/VAR-A http://localhost/PROJECT-A/VAR-A) VAR_PROJECT_A_VAR_B=$(curl http://localhost/PROJECT-A/VAR-B http://localhost/PROJECT-A/VAR-B) VAR_PROJECT_X_VAR_Q5_X= It will auto-complete it with the following, as expected: $(curl http://localhost/PROJECT-X/VAR-Q5-X http://localhost/PROJECT-X/VAR-Q5-X) It feels like Copilot understands the context in variety of programming languages and configuration formats. If you're writing a Docker Compose file and define a Redis service that contains the flag `--port 8888`, it will automatically offer to autocomplete your exposed ports with 8888:8888. Without the --port flag it will suggest 6379, which is the default port for Redis. These examples are trivial, but I find that these savings really add up and cut down on the amount of boilerplate and otherwise uninteresting busywork you have to do. Of course the copyright-violating aspects of Copilot are inexcusable, but I still find Copilot to be useful in other ways.