Refactoring Patterns - Part 2

1. Why do we refactor?

We refactor so we can clean up code, increase reusability, and remove 'code smells'

2. What's the difference between "refactoring" and "changing shit"?

When you refactor you are not changing what the code does. (i.e. implementing a new feature). "Changing shit" is for that or babies, depending on how you look at it. 

3. What role do patterns play in refactoring?

They give programmers a common way to discuss problems in code, and give the programmer an idea of what type of refactoring could work in a certain situation. Having different tools..what is the right one for the job.

4. Why do some refactoring patterns seem to be opposites?

Its conceptual though, so a benefit is different in each situation

5. Does refactoring always make code better?

No.