Refactor to Understand

• What was obvious to the author isn’t always obvious

• Break apart large methods

• Remove magic numbers / expressions

• GIVE GOOD NAMES

• Don’t worry about performance

Previous slide

Next slide

Back to first slide

View graphic version