This website uses cookies to ensure you get the best experience.
Learn more.
A developer wants Copilot to change a large legacy module. The first response makes many unrelated changes. Which next approach best reduces uncertainty?
Published
- Ask for the entire rewrite again but require twice as much generated code.
- Break the work into bounded steps, first adding characterization tests and then applying one requested change at a time.
- Tell Copilot to treat every proposed improvement as part of the original requirement.
- Remove all existing tests from the context to prevent the old design from influencing the rewrite.
Comments — 0
Sign in to comment