Develop your sense of code smell
Sep. 20, 2017•0 likes•1,225 views
Download to read offline
Report
Software
It has been 18 years since Martin Fowler published “Refactoring” which codified an initial catalog of code smells. But in that time, have our noses been able to sniff them out? What have we done to develop our sense of smell? We will do a series of Sparrow Decks to increase our sense of code smell by building the pattern recognition part of our brain. This way we can more easily know if there is something wrong with the code. Remember smelling you have a problem is always the first step. (Note: this technique works for non-programmers as well as programmers so even if you’re not a programmer, come and develop your sense of code smell!)
Mike ClementFollow
Recommended
Proof of lifeDavid Rothauser
A Testers Guide to the Myths, Legends and Tales of Unit TestingAsh Winter
Battledecks - California Library Association 2011 Patrick "PC" Sweeney
Data Mining Dissertations and Adventures and Experiences in the World of Chem...US Environmental Protection Agency (EPA), Center for Computational Toxicology and Exposure
Code Katas Spring 2012Mike Clement
Noam Kfir - There is no Java Script - code.talks 2015AboutYouGmbH
More Related Content
More from Mike Clement
Collaboration Principles from Mob ProgrammingMike Clement
Focus on Flow: Lean Principles in ActionMike Clement
Taming scary production code that nobody wants to touchMike Clement
Maps over Backlogs: User Story Mapping to Share the Big PictureMike Clement
Escaping the Pitfalls of Software Product DevelopmentMike Clement
Put the Tests Before the CodeMike Clement
Recently uploaded
Dido_Grigorov_Zurich_2020.pdfPlamenaDzharadat
What is Microsoft Power BI used for.pptxJohnCommuserv
Database storage engine internals.pptxAdewumiSunkanmi
Exploring GitHub Actions through EGAD: An Experience ReportESUG
How to fix JavaScript SEO problems on a scaleSerge Bezborodov
Semantic Search_ NLP_ ML.pdfPlamenaDzharadat
Develop your sense of code smell
- 1. Develop your Sense of Code Smell Mike Clement @mdclement Founding Software Craftsman at Greater Sum mike@softwareontheside.com http://blog.softwareontheside.com
- 2. Examples of smells in the physical world? Photo by freestocks.org on Unsplash
- 3. What if you couldn’t smell?
- 4. What if you learned to smell wrong?
- 5. What does that even mean?
- 6. Style Ira Glass video
- 7. Photo by henry fournier on Unsplas
- 8. Photo by Elijah Henderson on Unsplash
- 9. Practice makes…
- 10. Practice makes Permanent
- 12. Photo by Roksolana Zasiadko on Unsplash
- 14. Practice makes Permanent
- 16. High Quality, High Quantity Examples
- 17. Sparrow Decks
- 18. You have to try…
- 19. Yes you’re going to feel silly…
- 20. And you might be wrong…
- 21. And sometimes you WILL be wrong…
- 22. But trying is really important!
- 23. Sparrows
- 24. Win this book and a mechanical keyboard at the closing!
- 25. Code Smells • Long Method • 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 is maybe a misnomer Photo by freestocks.org on Unsplash
- 27. How do you get the necessary reps?
- 29. You have to try…
- 30. Yes you’re going to feel silly…
- 31. And you might be wrong…
- 32. And sometimes you WILL be wrong…
- 33. But trying is really important!
- 34. Long Line
- 35. Clutter
- 36. Photo by Doug Linstedt on Unsplash
- 37. Bad Names
- 38. You have to try…
- 39. Yes you’re going to feel silly…
- 40. And you might be wrong…
- 41. And sometimes you WILL be wrong…
- 42. But trying is really important!
- 43. But why Mike?
- 44. Why do I have to try?
- 45. Why do I have to try? Rat video
- 46. Long Method
- 47. Duplication
- 48. http://bit.ly/sparrowdecks Sparrow Decks
- 49. Code Smells • Long Method • 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’s Sparrow 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