'Code Smells - Developing Design Sense for your Code - Bad Names' by Llewellyn Falco

'In order to make delicious food,you must eat delicious food…. you need to develop a palate capable of discerning good and bad. Without good taste, you can't make good food.' - Jiro Ono (World’s Best Sushi Chef). The same is true for great code. If we want to make great code we need a refined palate for what great code looks like. We need to look at code and develop a sense for it’s properties and smells. Sadly this is rarely ever done. Programmers are expected to just 'know' what is good and what is bad with ever getting a chance to develop and curate an aesthetic sense. Worse, code is rarely looked at unless it is causing us problems so we are expected to be gourmets while spending our time eating at McDonalds. Come work on your sense of code. We will look at many snippets to compare and contrast different aspects of what good code is. Learning Outcomes: How to identify and correct, Clutter, Long lines, Long Methods, Bad Names, Duplication, Inconsistency.

Link: http://agiledayriga.lv/index.html#session13

Transcript

2. Good
4. Bad
6. Bad
8. Good
10. Bad
12. Bad
14. Good
16. Good
18. Bad
20. Good
22. Good
24. Good
26. Bad
28. Bad
30. Bad
32. Bad
34. Bad
36. Bad
38. Bad
40. Bad
42. Good
44. Bad
46. Good
48. Bad
50. Good
52. Bad
54. Bad
56. Good
58. Good
60. Bad
62. Good
64. Bad
66. Good
68. Bad
70. Bad
72. Good
74. Bad
76. Bad
78. Good
80. Good
82. Bad
84. Good
86. Bad
88. Bad
90. Good
92. Bad
94. Bad
96. Good
98. Good
100. Good
102. Bad
104. Good
106. Bad
108. Bad
110. Good
112. Good
114. Bad
116. Good
118. Bad
120. Bad
122. Good
124. Bad
126. Bad