Refactoring is the controllable process of systematically improving your code without writing new functionality. The goal of refactoring is to pay off technical debt. The mantra of refactoring is clean.
Much of refactoring is devoted to correctly composing methods. You can either refactor the tests themselves or write an entirely new set of higher-level tests. When to refactor how to refactor catalog code smells bloaters long method large class primitive obsession long parameter list data clumps object-orientation abusers switch statements.
Refactoring helps you understand other people’s code. If you have to deal with someone else’s dirty code, try to refactor it first. Clean code the main purpose of refactoring is to fight technical debt.
Full list of refactoring techniques and code smells. Once problem is determined, just pick a refactoring and follow it's instruction. Each pattern is like a blueprint that you can customize to solve a particular design problem in your code.
La refactorización es un proceso controlable de mejora del código sin crear nuevas funcionalidades.
