I did, thank you. Terms therein like "they spend more time prompting the AI" genuinely do not apply to a code copilot, like the one provided by GitHub, because it infers its prompt based on what you're doing and the context of the file and application and creates an autocomplete based on its chat completion, which you can accept or ignore like any autocomplete.

You can start writing test templates and it will fill them out for you, and then write the next tests based on the inputs of your methods and the imports in the test class. You can write a whole class without any copilot usage and then start writing the xmldocs and it will autocomplete them for you based on work you already did. Try it for yourself if you haven't already, it's pretty useful.