• codequality
• refactorit
• code-smell

Code smell | Side Effects

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

• codequality
• opinion

The importance of prioritizing code optimization for humans rather than machine

In this article I will present my arguments to justify why in most software projects it is more important to prioritize the optimization of code for humans rather than for machines.

• codequality
• refactorit
• code-smell
• testing

Code smell | Hardcoded fake data in tests

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

• codequality
• design-pattern

Design pattern | Criteria

This pattern allows you to build search queries using a common interface, which makes the code much more modular and flexible.

• codequality
• refactorit
• code-smell

Code Smell | Switch Statements

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

• codequality
• refactorit
• code-smell

Code Smell | Too Many Imports

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

• codequality
• refactorit
• code-smell

Code Smell | Magic Numbers

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

• codequality
• eslint

Standardize imports with ESLint

This rule of ESLint will help us maintain a standard regarding the ordering and grouping of the imports of our project.

• codequality
• refactorit
• code-smell

Code Smell | Data Clumps

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