In one of my previous post I talked about “Clean Frontend Architecture” and principles that should be followed in order to positively influence the maintainability and scalability of frontend applications.
This time I would like to show the most common “Code Smells” that I have come across in Angular.
So, what are “Code Smells“ and why are they so bad?
Well, I would say the best definition of “Code Smells” is:
The total count of WTFs during a code review.
One might also measure the Code Quality with this procedure. A reference for that would be the book “Clean Code“ by Robert C. Martin, where the Code Quality is defined by the WTFs/Minute.
Code quality measurement
But why are “Code Smells“ bad? Because they negatively influence the maintainability and/or performance of any application.
I have seen so many “Code Smells” and bad practices that I have to categorize them. But how can this be done? One approach would be to categorize them by their negative impact on the performance.