Series

Code Smells

In this series, we will see several symptoms and situations that make us doubt the quality of our developments. We will present possible solutions. Most are just clues. They are no hard rules.

Articles in this series

Code Smell 233 - Collections Count

Dec 1, 20232 min read43 views

You count collections or collections.count? · TL;DR: Chose narrow names Problems Bad Naming Solutions Accurately describe your...

Code Smell 233 - Collections Count

Code Smell 232 - Reusable Code

Nov 25, 20232 min read35 views

Don't Repeat Yourself. Don't Repeat Yourself TL;DR: You can find missing abstractions by looking at repeated code Problems DRY principle...

Code Smell 232 - Reusable Code

Code Smell 231 - Redundant Data

Nov 11, 20233 min read30 views

Where are your sources of truth? · TL;DR: Say it only once Problems Don't Repeat Yourself principle violation Consistency...

Code Smell 231 - Redundant Data

Code Smell 230 - Schrödinger Code

Nov 4, 20232 min read68 views

Your code is dead and alive · TL;DR: Look carefully for race conditions Problems Principle of Least Surprise violation Race...

Code Smell 230 - Schrödinger Code

Code Smell 229 - Red Tape

Oct 27, 20232 min read55 views

You overcomplicate your code · TL;DR: Avoid Accidental complexity and bureaucracy Problems Accidental Complexity Readability Bijection...

Code Smell 229 - Red Tape

Code Smell 228 - Multiple Classes per File

Oct 21, 20232 min read45 views

More than one class is a mess · TL;DR: Follow the separation of concerns principle and file organization Problems Code...

Code Smell 228 - Multiple Classes per File