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 247 - Javascript Replace

Apr 16, 20242 min read13 views

You want to replace all, but you replace one ocurrence · TL;DR: Bad function names will lead you to defects Problems Misleading Names The least...

Code Smell 247 - Javascript Replace

Code Smell 246 - Expiration Date

Apr 9, 20243 min read44 views

You need to model an expiration date. Which object will you use? · TL;DR: Model real word expiration dates with... expiration dates (I will use expiry...

Code Smell 246 - Expiration Date

Code Smell 245 - exec() and eval()

Apr 3, 20242 min read34 views

A great door for hackers · TL;DR: Don't use metaprogramming. It is not that cool Problems Security Limited Control Solutions Use direct calls...

Code Smell 245 - exec() and eval()

Code Smell 244 - Incomplete Error information

Mar 31, 20242 min read46 views

You show an error and provide no useful information · TL;DR: Help yourself and others with correction information Problems Debugging and maintenance...

Code Smell 244 - Incomplete Error information

Code Smell 243 - Concatenated Properties

Mar 15, 20242 min read52 views

You join independent information TL;DR: Don't mix ortoghonal behavior Problems Maintainability Error Prone Performance Penalties Premature...

Code Smell 243 - Concatenated Properties

Code Smell 242 - Zombie Feature Flags

Feb 21, 20243 min read74 views

Feature flags are evil... and sometimes come back as zombies TL;DR: Don't leave dead unused code. Clean your flag mess. Problems Dead...

Code Smell 242 - Zombie Feature Flags