**Code Smells** are often signs that refactoring could be needed. That is not always the case, but these "smells" should be looked at further to dethermine if there is a need for refactoring.
**Code Smells** are often signs that refactoring could be needed. That is not always the case, but these "smells" should be looked at further to determine if there is a need for refactoring.
* Solution: It may be possible to break these conditionals up into smaller, more conscise methods that are easier to read and have a clear purpose.
**Reocurring Parameter lists**
* Force: Refactoring may be considered if a certian list of parameters keeps reappearing in many methods.
For example:
```
function(int a, int b, string c)
function2(int a, int b, string c)
function3(int a, int b, string c)
```
* Solution: It may be possible to group these parameters into an object and instead pass the object around to different functions rather than passing each parameter.