cgrings-csw / refactoring-senior-training Goto Github PK

• Is your code easy to change?
• Do you get near-instant feedback when you change it?
• Do you understand?

If your answer to these questions is "no", you have legacy code and it is consuming time and money from your development.

There are several patterns that can be applied in the refactoring of your code, and these patterns we will be applying in this project, and I believe it will help many to give more useful life to their legacy projects, more performance, more functionality, more reliability and more ability to management.

The main reason for code refactoring is to improve the maintainability of the software, as well as to make existing code easier to understand.

• Understand the process and principles of refactoring.
• Quickly apply convenient refactorings to make a program easier to understand and easier to change.
• Recognize "bad smells" in code that signal opportunities to refactor.
• Explore the refactorings, each with its own explanation, mechanism.
• Write robust tests or your refactorings.

Refactoring

Contribution guide

• Fork a Github repository.
• Clone the forked repository to your local system.
• Add a Git remote for the original repository.
• Create a feature branch in which to place your changes.
• Push the branch to GitHub.
• Open a pull request from the new branch to the original repo.)
• Clean up after your pull request is merged.

Branch created to keep the previous project so that others can perform their proper refactoring tests

⚠️Warning⚠️

The project is receiving merges of the changes made on the developer branch, and in the comments of the pull requests there is a reference to each class that is being refactored.

If you want to have the project in its original state, just fork the repository in the title of this document. If the original repository for this project no longer exists, you can find it inside my own repository "Before Refactoring System".