Code Smells in Angular

In one of my previous post I talked about “<a href="https://blog.bitsrc.io/clean-frontend-architecture-2995c68702fb" rel="noopener ugc nofollow" target="_blank">Clean Frontend Architecture</a>” and principles that should be followed in order to positively influence the maintainability and scalability of frontend applications. <blockquote> This time I would like to show the most common “Code Smells” that I have come across in Angular. </blockquote> <h2>So, what are “Code Smells“ and why are they so bad?</h2> Well, I would say the best definition of “Code Smells” is: <blockquote> The total count of WTFs during a code review. </blockquote> 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. <img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*LEyqjbNuLqpuRRDlqCY2Fw.png" style="height:551px; width:700px" /> 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.  <a href="https://blog.bitsrc.io/code-smells-in-angular-ce73bf7db072">Website</a>