Code Smell 321 - Getter Piggybacking
One broken window invites another
Aug 20, 20266 min read43

Search for a command to run...

Series
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.
One broken window invites another

Brushing Over Real Problems

Don't turn collaborators into permanent roommates

You polish code that nobody touches while the real hotspots burn

Your system trusts UI input and sends security emails to attacker-controlled addresses instead of database values

When syntax noise hides real design problems
