Blog

Understanding why using generic exceptions is a code smell and how it can make error handling difficult.

Avoid complex if conditions by using variables or functions to improve readability and maintainability.

Avoid the code smell called "Chained Ternary Operators" by replacing them with switch statements and object maps for cleaner, more efficient code.

This code smell can be detected when a function modifies an external state beyond its own scope.

this code smell occurs when you see fake data that is needed for tests within the same test file.

This code smell is caused by the abusive use of the switch statements.

This code smell is caused by the abusive use of imports in components, classes or any other type of module of our project.

This code smell can be detect when we use a number that lacks the proper semantics.

This code smell can be detected when we observe that certain groups of data are being used in different parts of our code.

This code smell can be detected if making a change have to replicate this change in different parts of our code.

This smell can be detected when we observe that at a specific point in our application we perform too many changes, these points can be a certain class, a .js or .ts file that exports certain functions, etc.

This code smell is given by the abusive use of primitive types when modeling our classes.