'Code Smells - Developing Design Sense for your Code - Inconsistency' 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. Duplication
4. Inconsistency
6. Duplication
8. Inconsistency
10. Duplication
12. Duplication
14. Duplication
16. Inconsistency
18. Inconsistency
20. Duplication
22. Inconsistency
24. Duplication
26. Duplication
28. Duplication
30. Inconsistency
32. Duplication
34. Duplication
36. Inconsistency
38. Inconsistency
40. Inconsistency
42. Duplication
44. Inconsistency
46. Inconsistency
48. Inconsistency
50. Inconsistency
52. Inconsistency
54. Duplication
56. Inconsistency