Take control of your application's behavior and move toward dependency injection by refactoring your existing code.

Do you want to optimize your code with AI? Check out how you can use Copilot to Refractor Code and improve the way you write code.

Refactoring plays a critical role in maintaining a codebase that allows for rapid development, but it’s important to not to view this, and code quality, as an isolated process.

Without skilled developers supervising AI coding assistants, they are likely to break your code rather than write it. Right now, only people can fine-tune and evaluate AI.

Ondrej Balas continues his series on refactoring code for dependency injection, looking at patterns and strategies for changing application behavior after it has already been compiled.

The result was a new data model for code (called the Lossless Semantic Tree) and a rules-based refactoring engine driven by recipes that specify how to rewrite the code.

Change the code to use current code conventions (again using refactoring tools). Start to extract functionality into meaningful routines. Start to add tests where possible (not often possible).

When you're refactoring legacy code, it doesn't matter if some of the tests you write happen to contradict ideal specifications. What matters is that they test the program's current behavior.

From Sri Lanka comes an academic report saying you probably shouldn't even bother to refactor -- if code quality is your primary concern.

At Ignite 2019, Microsoft shared that Visual Studio IntelliCode now has whole-line code completions and features dynamic refactoring detection.