Code Smell 48 — Code Without Standards
Working on a solo project is easy. Unless you go back to it after some months. Working with many other developers requires some agreements.
- Automate your styles and indentation.
- Enforce agreed policies.
Correct sample taken from Sandro Mancuso’s bank kata
The right example has several other smells, but we keep it loyal to its GIT version in order to show only code standardization issues.
Linters and IDEs should test coding standards before a merge request is approved.
We can add our own naming conventions related to Objects, Classes, Interfaces, Modules etc.
Use coding standards in your projects.
A well-written clean code always follows standards about naming conventions, formatting and code style.
Such standards are helpful because they make things clear and deterministic for the ones who read your code, including yourself.
Code styling should be automatic and mandatory on large organizations to enforce Collective Ownership.
Code Smell 06 — Too Clever Programmer
Code difficult to read. Tricky with names without semantic. Sometimes using language’s accidental complexity.
The nice thing about standards is that there are so many to choose from.
Andrew S. Tannenbaum
This article is part of the CodeSmell Series.