-The concept of bad smells. What are bad smells? Well, we - -2
-mentioned earlier that refactoring is typically applied when there is something - -3
-that does not look right, does not feel right in the - -4
-code. And that's exactly what bad smells are. Bad smells, or - -5
-code smells if you wish, are symptoms in the code of - -6
-a program that might indicate deeper problems. So there might be - -7
-parts of my system, classes in my systems, that just don't - -8
-smell right, and it feels like there's, there might be something wrong - -9
-with them. And if you are an experienced developer just like Brad, - -10
-you'll be able to figure out there is something wrong with the - -11
-classes. You'll be able to smell that there's something wrong and you'll - -12
-do something about it. And I want to mention one more, just to make - -13
-sure that we're all on the same page here. That these bad - -14
-smells are usually not bugs and don't prevent the program from functioning. They - -15
-however indicate weaknesses in the design of the system that might cause - -16
-problems during maintenance. In other words, - -17
-they might make the code less maintainable, - -18
-harder to understand, and so on. Just like refactorings, - -19
-there's also many possible different bad smells. So what - -20
-I'm providing here is just a possible list of - -21
-some very common bad smells. And you can find plenty - -22
-of information on this online. So what I want - -23
-to do next is just to cover before finishing the - -24
-lesson a few of those to show you some - -25
-examples of smells and what you can do about them. -- cgit 1.4.1