- by Martin Fowler
- recommended in π° Every Actionable Book is Actually Two Books Inside
- about refactoring, I'd presume
-
~ code only needs to be refactored if it needs to be changed
- ~ first step of refactoring is always ensuring a solid test suite
-
~ test often to reduce what you have to change back if something breaks
-
~ prepend parameter names with an indefinite article unless the object has a specific role
-
~ judging the performance of parts of code is hard and unintuitive
π Refactoring: Improving the Design
Backlinks
- ~ call the return value of a function "result"
- ~ code only needs to be refactored if it needs to be changed
- ~ first step of refactoring is always ensuring a solid test suite
- ~ prepend parameter names with an indefinite article unless the object has a specific role
- ~ test often to reduce what you have to change back if something breaks
This is a Book note.