about summary refs log tree commit diff
path: root/usth/ICT2.7/P4L5 Software Refactoring Subtitles/21 - Bad Smells - lang_en_vs4.srt
diff options
context:
space:
mode:
Diffstat (limited to 'usth/ICT2.7/P4L5 Software Refactoring Subtitles/21 - Bad Smells - lang_en_vs4.srt')
-rw-r--r--usth/ICT2.7/P4L5 Software Refactoring Subtitles/21 - Bad Smells - lang_en_vs4.srt99
1 files changed, 99 insertions, 0 deletions
diff --git a/usth/ICT2.7/P4L5 Software Refactoring Subtitles/21 - Bad Smells - lang_en_vs4.srt b/usth/ICT2.7/P4L5 Software Refactoring Subtitles/21 - Bad Smells - lang_en_vs4.srt
new file mode 100644
index 0000000..240d37b
--- /dev/null
+++ b/usth/ICT2.7/P4L5 Software Refactoring Subtitles/21 - Bad Smells - lang_en_vs4.srt
@@ -0,0 +1,99 @@
+1

+00:00:00,070 --> 00:00:03,450

+The concept of bad smells. What are bad smells? Well, we

+

+2

+00:00:03,450 --> 00:00:06,700

+mentioned earlier that refactoring is typically applied when there is something

+

+3

+00:00:06,700 --> 00:00:09,130

+that does not look right, does not feel right in the

+

+4

+00:00:09,130 --> 00:00:12,260

+code. And that's exactly what bad smells are. Bad smells, or

+

+5

+00:00:12,260 --> 00:00:15,320

+code smells if you wish, are symptoms in the code of

+

+6

+00:00:15,320 --> 00:00:18,868

+a program that might indicate deeper problems. So there might be

+

+7

+00:00:18,868 --> 00:00:21,775

+parts of my system, classes in my systems, that just don't

+

+8

+00:00:21,775 --> 00:00:25,309

+smell right, and it feels like there's, there might be something wrong

+

+9

+00:00:25,309 --> 00:00:29,010

+with them. And if you are an experienced developer just like Brad,

+

+10

+00:00:29,010 --> 00:00:31,320

+you'll be able to figure out there is something wrong with the

+

+11

+00:00:31,320 --> 00:00:33,950

+classes. You'll be able to smell that there's something wrong and you'll

+

+12

+00:00:33,950 --> 00:00:36,880

+do something about it. And I want to mention one more, just to make

+

+13

+00:00:36,880 --> 00:00:39,270

+sure that we're all on the same page here. That these bad

+

+14

+00:00:39,270 --> 00:00:43,070

+smells are usually not bugs and don't prevent the program from functioning. They

+

+15

+00:00:43,070 --> 00:00:46,190

+however indicate weaknesses in the design of the system that might cause

+

+16

+00:00:46,190 --> 00:00:48,480

+problems during maintenance. In other words,

+

+17

+00:00:48,480 --> 00:00:50,440

+they might make the code less maintainable,

+

+18

+00:00:50,440 --> 00:00:53,650

+harder to understand, and so on. Just like refactorings,

+

+19

+00:00:53,650 --> 00:00:56,610

+there's also many possible different bad smells. So what

+

+20

+00:00:56,610 --> 00:00:59,160

+I'm providing here is just a possible list of

+

+21

+00:00:59,160 --> 00:01:02,190

+some very common bad smells. And you can find plenty

+

+22

+00:01:02,190 --> 00:01:04,349

+of information on this online. So what I want

+

+23

+00:01:04,349 --> 00:01:06,910

+to do next is just to cover before finishing the

+

+24

+00:01:06,910 --> 00:01:08,700

+lesson a few of those to show you some

+

+25

+00:01:08,700 --> 00:01:11,140

+examples of smells and what you can do about them.