The impact of conversation smells

What if we applied the same approach that we use for our code smells to our spoken and written language?

As an experienced developer, recognizing code smells is one of the easy parts of code reviews. If your organization is large enough, you might have a static code analysis tool in IDE such as ReSharper, or in your SDLC pipeline such as Sonarqube, to help with identifying and recommending solutions automatically. These tools not only catch the problem, but they teach by recommending a solution with supporting evidence. Isn’t automation great? 

For those wondering about what code smells are, they are code that indicates there is an underlying problem: be it inefficient code, misused coding principles/patterns, or duplication of code.

Join LeadDev.com for free to access this content