How do we Refactor?
Refactoring can be triggered by many factors such as deeper understandings, changes in requirements and so on. But never try to break into large quantities of code and refactor. We’ll end up in a much worse position than we are.
Refactoring has to be done slowly, deliberately and carefully. Below are some guidelines for refactoring given by Martin Fowler:
While refactoring, fix the code and everything depends on the code. This will a pain. But it’s going to hurt more later.
- summary of Refactoring, from The Pragmatic Programmer: from Journeyman to Master
Refactoring can be triggered by many factors such as deeper understandings, changes in requirements and so on. But never try to break into large quantities of code and refactor. We’ll end up in a much worse position than we are.
Refactoring has to be done slowly, deliberately and carefully. Below are some guidelines for refactoring given by Martin Fowler:
- Don’t try to add functionality and refactor at the same time.
- Have good tests before refactoring. It’ll help us to detect if anything breaks.
- Take short steps.
While refactoring, fix the code and everything depends on the code. This will a pain. But it’s going to hurt more later.
- summary of Refactoring, from The Pragmatic Programmer: from Journeyman to Master
No comments:
Post a Comment