Best is to put the expected value last, if conditions you want to write.

TL;DR: In a natural way, write your conditions.

Problems

• Readability

• The least surprise principle violation

Solutions

1. Write your conditions with the expected value as the second.

2. Name the variables accordingly.

Context

Most programmers write the variable or condition first and the test value second.

In fact, this is the correct order for assertions.

In some languages, this style is used to avoid accidental assignment instead of equality comparison, which can result in a logic error in the code.

Sample Code

Wrong

if (42 == answerToLifeMeaning) {
  // 
}

Right

if (answerToLifeMeaning == 42) {
  // might be mistaken with answerToLifeMeaning = 42
}

Detection

We can check for constant values on the first side of the comparison.

Tags

• Readability

Conclusion

Reliable, direct, and clear be when conditions your writing.

Relations

Code Smell 99 – First Second

Maxi Contieri ⭐⭐⭐ ・ Nov 1 ’21 ・ 1 min read

#oop
#tutorial
#webdev
#cleancode

Disclaimer

Code Smells are just my opinion.

Credits

Photo by Lia on Unsplash

Any man can make mistakes, but only an idiot persists in his error.

Marcus Cicero

Software Engineering Great Quotes

Maxi Contieri ⭐⭐⭐ ・ Dec 28 ’20 ・ 13 min read

#codenewbie
#programming
#quotes
#software

This article is part of the CodeSmell Series.

How to Find the Stinky parts of your Code

Maxi Contieri ⭐⭐⭐ ・ May 21 ’21 ・ 8 min read

#codenewbie
#tutorial
#codequality
#beginners