Downloaded 25 times
Uploaded byMike Clement
Develop your sense of code smell
The document discusses the concept of 'code smells,' which indicates issues in code like long methods, large classes, and duplicate code. It emphasizes the importance of practice in recognizing and addressing these smells to improve software quality. Various resources and examples are provided to aid in understanding and applying these concepts.
More Related Content
Similar to Develop your sense of code smell
More from Mike Clement
Develop your sense of code smell
- 1. Develop your Senseof Code Smell Mike Clement @mdclement Founding Software Craftsman at Greater Sum mike@softwareontheside.com http://blog.softwareontheside.com
- 2. Examples of smellsin the physical world? Photo by freestocks.org on Unsplash
- 3. What if youcouldn’t smell?
- 4. What if youlearned to smell wrong?
- 5. What does thateven mean?
- 6.
- 7. Photo by henryfournier on Unsplas
- 8. Photo by ElijahHenderson on Unsplash
- 9.
- 10.
- 12. Photo by RoksolanaZasiadko on Unsplash
- 14.
- 16. High Quality, HighQuantity Examples
- 17.
- 18. You have totry…
- 19. Yes you’re goingto feel silly…
- 20. And you mightbe wrong…
- 21. And sometimes youWILL be wrong…
- 22. But trying isreally important!
- 23.
- 24. Win this bookand a mechanical keyboard at the closing!
- 25. Code Smells • LongMethod • Large Class • Primitive Obsession • Long Parameter List • Data Clumps • Alternative Classes with Different Interfaces • Refused Bequest • Switch Statements • Temporary Field • Divergent Change • Parallel Inheritance Hierarchies • Shotgun Surgery • Comments • Duplicate Code • Data Class • Dead Code • Lazy Class • Speculative Generality • Feature Envy • Inappropriate Intimacy • Incomplete Library Class • Message Chains • Middle Man
- 26. Code smell ismaybe a misnomer Photo by freestocks.org on Unsplash
- 27. How do youget the necessary reps?
- 29. You have totry…
- 30. Yes you’re goingto feel silly…
- 31. And you mightbe wrong…
- 32. And sometimes youWILL be wrong…
- 33. But trying isreally important!
- 34.
- 35.
- 36. Photo by DougLinstedt on Unsplash
- 37.
- 38. You have totry…
- 39. Yes you’re goingto feel silly…
- 40. And you mightbe wrong…
- 41. And sometimes youWILL be wrong…
- 42. But trying isreally important!
- 43.
- 44. Why do Ihave to try?
- 45. Why do Ihave to try? Rat video
- 46.
- 47.
- 48.
- 49. Code Smells • LongMethod • Large Class • Primitive Obsession • Long Parameter List • Data Clumps • Alternative Classes with Different Interfaces • Refused Bequest • Switch Statements • Temporary Field • Divergent Change • Parallel Inheritance Hierarchies • Shotgun Surgery • Comments • Duplicate Code • Data Class • Dead Code • Lazy Class • Speculative Generality • Feature Envy • Inappropriate Intimacy • Incomplete Library Class • Message Chains • Middle Man
- 50. Resources • Llewellyn Falco’sSparrow Decks: http://llewellynfalco.blogspot.com/p/sparrow-decks.html • Kathy Sierra on Making Badass Developers: https://www.youtube.com/watch?v=FKTxC9pl-WM • Smell Descriptions online: https://refactoring.guru/refactoring/smells
- 51. Mike Clement • @mdclement •mike@softwareontheside.com • https://github.com/mdclement • Slides at: http://blog.softwareontheside.com • Greater Sum • @thegreatersum • http://www.greatersum.com • Software Craftsmanship Atlanta • Find us on meetup.com