6.1. Enhancing Productivity and Code Quality
💡 First Principle: Copilot's real productivity lever is reducing cognitive friction, not keystrokes. It drafts boilerplate, explains unfamiliar code in place, and proposes refactors — freeing your attention for the judgment work only a human can do.
Why this matters: exam questions describe a developer task and ask how Copilot helps. The strong answers identify the friction Copilot removes (a context switch avoided, boilerplate generated, a draft to react to) rather than overstating it as autonomous correctness.
The mental model: a fast, well-read assistant who hands you drafts. The value isn't that they type quickly; it's that you start from a draft and a second opinion instead of a blank file, while you remain the editor.
⚠️ Common Misconception: "Copilot's main benefit is typing speed." The major gains come from reduced context switching, faster learning in-editor, refactoring, documentation, and test generation. Saved keystrokes are the most visible benefit, not the biggest one.
