I would disagree. Just like an airplane copilot, GitHub Copilot really shines in rote work: when it can correctly infer what you are about to do, it can and wil

I would disagree. Just like an airplane copilot, GitHub Copilot really shines in rote work: when it can correctly infer what you are about to do, it can and will assist you correctly. It’s not able to make big decisions, but in a pinch, it might be able to give hints. In short: Write your class methods or functions headers-first and then start working on the bodies. Add step-by-step comments to a body before starting to add code. These are, of course, good habits to foster even without Copilot. Copilot will pick up what you do in the first method/function/whatever structure and suggest adapted completions for the rest. In general, when there are multiple similar things to write, name your cases, then write one of them in detail, move to the next empty one and watch magic happen. If used right, Copilot can give developers a significant velocity boost, especially in greenfield projects where there is lots and lots of boilerplate to write. It is still a ”copilot” though so keep an eye on it, lots of ”wtf is that guy doing” moments ahead for sure.