A developer wants Copilot to change a large legacy module. The first response makes many unrelated changes. Which next approach best reduces uncertainty?

Published
  1. Ask for the entire rewrite again but require twice as much generated code.
  2. Break the work into bounded steps, first adding characterization tests and then applying one requested change at a time.
  3. Tell Copilot to treat every proposed improvement as part of the original requirement.
  4. Remove all existing tests from the context to prevent the old design from influencing the rewrite.

Comments — 0