36. Detecting Code Smells & Anti-Patterns

💡

Code smells are early indicators of potentially poor object-oriented design. If we know how to spot code smells, we can make better design decisions by understanding and managing the tradeoffs involved in occasionally breaking rules, principles, and the philosophy of RDD.

Chapter goals

In this chapter, we will aim to:

  • Understand the difference between signs of complexity, code smells, and anti-patterns
  • Understand the five different categories of code smells
  • Learn how the rules of object calisthenics help prevent code smells
  • See practical TypeScript examples of each major code smell category, along with refactored versions
  • …

Howdy 👋

This is an online wiki about the main topics over the last 40 years of software design, architecture & testing. It was created by Khalil Stemmler.

This wiki's mission is to help eliminate the unknown unknowns, helping you get up to speed on the best practices and principles to write testable, flexible, and maintainable code.

I created this wiki while I was connecting the dots on my own path. You can read more about that learning journey in the introduction

Already bought it?

If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.

Want access?

You can read the intro to the book for free and visit solidbook.io to buy the book/wiki! To get an idea of my writing, read some of my best free content here and here.

Need help?

Something not working? Have a question? You can reach me on at khalil@khalilstemmler.com.